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: 5733ddf49ff49cd1f5e22fb4a9f815313eceb4780c03c3e0f2702b97dae88060
Public Swagger UI/API detected at path: /api/swagger.json - sample paths:
DELETE /api/v0/orders/items/{orderItemId}
GET /.well-known/jwks.json
GET /api/v0/roles
GET /api/v0/users/{id}
GET /api/v0/users/{id}/registration
GET /api/v0/users/{id}/volunteer
GET /api/v0/users/{userId}/roles
GET /api/v0/volunteers/departments
POST /api/v0/dealers/search
POST /api/v0/orders/items/{orderItemId}/revoke
POST /api/v0/orders/search
POST /api/v0/registration/search
POST /api/v0/roles/{roleId}/users
POST /api/v0/users
POST /api/v0/users/notes/search
POST /api/v0/users/search
POST /api/v0/volunteers/search
POST /api/v0/vouchers/search
PUT /api/v0/users/{userId}/roles/{roleId}