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: 5733ddf49ff49cd110a331ec8419566e6934d861c42d9ff266abb1ef3fa1732c
Public Swagger UI/API detected at path: /v2/api-docs - sample paths:
GET /api/ipay/validate
GET /api/ipay/verify
GET /epaisa/validate
GET /health
GET /mpesa/callback
GET /payment-wallet/v1/mafpay/balance
GET /payment-wallet/v1/mafpay/txn/details
GET /payment-wallet/v1/mafpay/txn/history
GET /payment-wallet/v2/mafpay/txnhistory
GET /wallet-dashboard/v3/{wallet}
GET /wallet-dashboard/v3/{wallet}/history
GET /wallet/v1/{paymentOption}
POST /api/ipay/fullrefund
POST /api/ipay/initiator
POST /api/ipay/initpush
POST /api/ipay/partialrefund
POST /api/ipay/refund
POST /api/ipay/search
POST /api/ipay/stkpush
POST /api/ipay/transact
POST /epaisa/inquiry
POST /epaisa/payment
POST /epaisa/reversal
POST /payment-wallet/v1/mafpay/adjust-credit-debit
POST /payment-wallet/v1/mafpay/create/wallet
POST /wallet/v1/transaction