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: 5733ddf49ff49cd151e75e4bf7196a6277abb2f7f32f532941be7637ee8a5c22
Public Swagger UI/API detected at path: /v3/api-docs - sample paths:
GET /clients
GET /clients/{id}
GET /employees
GET /employees/getLocationId/{oid}
GET /employees/{id}
GET /environmentConfig
GET /locations
GET /locations/{id}
GET /microsoftGraph/syncAzureActiveDirectory
GET /notifications
GET /smartwatchApi/Device/Login/{deviceUniqueNumber}
GET /smartwatchApi/Target/V2/Start
GET /smartwatchApi/getNewWalkSettings/{walkId}
GET /smartwatches
GET /smartwatches/available
GET /smartwatches/{id}
GET /walks
GET /walks/active
GET /walks/{walkId}
POST /smartwatchApi/Panic
POST /smartwatchApi/Pulse
POST /smartwatchApi/Target/Logs
POST /smartwatchApi/wristAlarm
PUT /notifications/{notificationId}
PUT /walks/finish