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: 5733ddf49ff49cd1aad03549ecf21ef25660abf8e67f7dab415d7f77c6ef98e3
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/About
GET /api/About/date
GET /api/About/{id}
GET /api/History
GET /api/History/date
GET /api/History/{id}
GET /api/News
GET /api/News/{id}
GET /api/auth/check
GET /api/auth/stsloginurl
GET /api/auth/stslogouturl
GET /api/news/{id}/publications
GET /api/profile
GET /api/system/info
GET /auth/check
GET /auth/stsloginurl
GET /auth/stslogouturl
POST /api/About/publish
POST /api/History/publish
POST /api/Images/fetch
POST /api/Images/upload
POST /api/auth/refreshtokens
POST /api/auth/tokens
POST /auth/refreshtokens
POST /auth/tokens