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: 5733ddf49ff49cd1b885ff43a81ce88f562b774ca7894bf46905fba96905fba9
Public Swagger UI/API detected at path: /swagger.json - sample paths: GET /coupons GET /coupons/hascoupon GET /coupons/verify GET /language
Open service 45.154.183.183:443 ยท colorwithwill.com
2025-12-20 08:13
HTTP/1.1 403 Forbidden Date: Sat, 20 Dec 2025 08:13:00 GMT Content-Type: text/html Content-Length: 118 Connection: close X-Varnish: 20892540 Age: 0 Via: 1.1 varnish (Varnish/6.3) section-io-cache: Miss section-io-id: e78e1721010c38a83b4bf6eb36d2fc6b Page title: 403 Forbidden <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> </body> </html>