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: 5733ddf49ff49cd1f3d88d60ad4d1c2fae919ac3d454553f108e7cf546c5bffc
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths:
GET /api/Activities
GET /api/Locations
GET /api/Locations/{id}
GET /api/Locations/{id}/Activities
GET /api/Permissions
GET /api/Permissions/{id}
GET /api/Sites
POST /api/DeliveryNotes
POST /api/Invoices
POST /api/Users
POST /api/Users/CheckInvitationValidity
POST /api/Users/CheckUserExistence