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: 5733ddf49ff49cd1aad03549a1d4f85bd1e16e38b760b2e08ab51ca3110716fa
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /confirm/{hash}
GET /connect/authorize
GET /connect/logout
GET /connect/userinfo
GET /healtCheck
GET /reset/{hash}
POST /connect/token