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: 5733ddf49ff49cd1aad03549192db818735b60360408418fdfeeafe24cf01d9d
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /api/EndPage/cr-s2s GET /api/Tracking/pixel GET /api/Tracking/redirectbackpixel POST /api/CompleteSurvey/CaptureUrlTimes POST /api/CompleteSurvey/VerifyIdentity POST /api/EndPage POST /api/Error/UserflowGlobalErrorHandler POST /api/Qualification/GetQualificationQuestion POST /api/Qualification/SaveQualification POST /api/Qualification/ValidateSecurity POST /api/Session POST /gmos2s
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549192db818735b60360408418f48c27745dfecd2c9
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /api/EndPage/cr-s2s GET /api/Tracking/pixel GET /api/Tracking/redirectbackpixel POST /api/EndPage POST /api/Error/UserflowGlobalErrorHandler POST /api/Qualification/GetQualificationQuestion POST /api/Qualification/SaveQualification POST /api/Qualification/ValidateSecurity POST /api/Session POST /gmos2s