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: 5733ddf49ff49cd1aad03549d6e5b37747e249be1ac1c9c9b3ca5c5201778341
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /integration/report/File/getfile/{id}
GET /integration/{siteName}/AdHocInspection/Get
GET /integration/{siteName}/WorkOrder/Get
GET /integration/{siteName}/WorkOrder/Get/{id}
GET /integration/{siteName}/WorkOrder/GetWithInspections/{id}
GET /integration/{siteName}/WorkOrder/Inspections/{id}
POST /integration/{siteName}/Tag/Post
POST /integration/{siteName}/WorkOrder/Post
PUT /integration/{siteName}/Tag/Put/{id}
PUT /integration/{siteName}/WorkOrder/Status/{id}