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: 5733ddf49ff49cd1aad035493b3b7350113b6f03966b42346d2beb74bffe4f6c
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /
GET /AddressLookup
GET /EmailPreferences
GET /Guidances
GET /Guidances/{id}
GET /Illnesses
GET /Illnesses/{id}
GET /Images/{filePath}
GET /Medications
GET /Medications/{id}
GET /Messages
GET /Messages/Unread
GET /Messages/{id}
GET /Patients
GET /SurveyResponses/overview
GET /SurveyResponses/overview/{id}
GET /SurveyResponses/{id}
POST /Contact
POST /Patients/registerDevice
POST /Unsubscribe
Severity: info
Fingerprint: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html