Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354910644b845b692a8244b7b53f480e545ee97314fb
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /ManagementArea/load/{managementAreaLoadId}
DELETE /NetworkShapefile/deleteshapefileload/{fileId}
DELETE /Region/role/{roleId}
GET /Authorisation
GET /Cycle/getOrgCycles
GET /Cycle/roles
GET /Dashboard/managementAreasPerRegion/{cycleId}
GET /ManagementArea/cycle/{cycleId}
GET /ManagementArea/detail/{managementAreaId}
GET /ManagementArea/extent/{managementAreaId}
GET /ManagementArea/managementAreaTypesFromProgramManagementAreas/{cycleId}
GET /ManagementArea/types/{cycleId}
GET /Map/wmsBase64
GET /NetworkShapefile/getShapefileDataSearchAttributeKeysByFileId/{fileId}
GET /NetworkShapefile/getShapefileLayers
GET /NetworkShapefile/layers/{organisationId}
GET /Preference
GET /Program/cycle/{cycleId}
GET /Program/programDetail/{programId}/{managementAreaId}
GET /Program/programNameProgramType/{cycleId}
GET /Program/programTypes
GET /Program/programsByManagementAreaId/{managementAreaId}
GET /Region/cycle/{cycleId}
GET /Region/organisation/{organisationId}
GET /Region/regionFromProgramManagementAreas/{cycleId}
GET /Report/tableau
POST /Asset/fetch
POST /Cycle/create
POST /Cycle/update
POST /Dashboard/assetTasks
POST /Dashboard/programManagementAreas
POST /Dashboard/spanPerformanceValues
POST /ManagementArea/load
POST /NetworkShapefile/fetchShapefilesByShapefileDataIds
POST /NetworkShapefile/load
POST /NetworkShapefile/updateshapefileload
POST /Region/create
POST /Region/roleRegion/{roleId}
POST /Region/roleRegionCycle
POST /Search/create
POST /Search/fetch
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035493c09a6c660038f3bc14fd59fc96f90ea22682d01
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /Asset/types GET /Program GET /Program/ManagementArea GET /Program/ManagementAreas GET /Task/approval/status GET /Task/company GET /Task/types POST /Asset POST /Task PUT /ProgramAsset/updateClearOfHazardAndCompletionDate