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: 5733ddf49ff49cd1aad035493b4e12a2877de10b5daa88fae77dc636309a91af
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/dtsapi/GetAssignedWorkerDropdownData
GET /api/dtsapi/GetContractDropdownData
GET /api/dtsapi/{id}
PATCH /api/dtsapi/UpdateDTSTicket
POST /api/dtsapi/CreateDTSTicket