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 · nextchapterstore.com
2025-12-22 07:49
HTTP/1.1 403 Forbidden Date: Mon, 22 Dec 2025 07:49:48 GMT Content-Type: text/html Content-Length: 118 Connection: close X-Varnish: 22655016 Age: 0 Via: 1.1 varnish (Varnish/6.3) section-io-cache: Miss section-io-id: 10d1ecdc644f621000c6e7b802c57f1a Page title: 403 Forbidden <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> </body> </html>
Open service 45.154.183.183:443 · nextchapterstore.com
2025-12-20 08:16
HTTP/1.1 403 Forbidden Date: Sat, 20 Dec 2025 08:16:18 GMT Content-Type: text/html Content-Length: 118 Connection: close X-Varnish: 22295114 Age: 0 Via: 1.1 varnish (Varnish/6.3) section-io-cache: Miss section-io-id: 643d38042b50ae67d6fd84fa308d2fc4 Page title: 403 Forbidden <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> </body> </html>