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: 5733ddf49ff49cd1aad035493b3b73505ce2d0d79f3afb43bca5c6c6c69e73d3
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /
GET /GetStatus
GET /GetStatusMetrics
GET /Stream
POST /ConnectConversations
POST /DisconnectConversations
POST /MarkMessageStatuses
POST /MarkSenderActions
POST /Status
POST /Status/{botId}
POST /vonage/{botId}/sms/status