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: 5733ddf49ff49cd1aad03549733d818175d71e449522fb830404cba2fee8b7c6
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/DistributorFunding
GET /api/v1/Loans/{loanId}
GET /api/v1/Loans/{loanId}/orders
GET /api/v1/Orders
GET /api/v1/Orders/GetLoanOrderDetails/{loanId}
GET /api/v1/Orders/GetOrderDetails/{orderId}
GET /api/v1/Orders/reasons/counter
GET /api/v1/Orders/reasons/deny
GET /api/v1/Orders/{orderId}
GET /api/v1/Partners/{partnerId}
POST /api/v1/Orders/changePayee
POST /api/v1/Orders/export
POST /api/v1/Orders/{orderId}/Submit
POST /api/v1/Orders/{orderId}/approve
POST /api/v1/Orders/{orderId}/counter
POST /api/v1/Orders/{orderId}/deny
POST /api/v1/webhook