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: 5733ddf49ff49cd1aad03549d0e213394c5769528880c6d75423a52fefa47ccc
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/params
GET /api/params/{parameters}/value
GET /api/params/{parameter}/details
PATCH /api/params/{parameter}/value
PUT /api/params/{parameter}