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: 5733ddf49ff49cd1f3d88d60f5975b931c9e493c37c453e96279c2b5f3acea5f
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths: GET /api/v1/Menu GET /api/v1/Page GET /api/v1/Page/view GET /api/v1/Preview GET /api/v1/Sitemap POST /api/v1/LinkRules POST /api/v1/Preview/content
Open service 104.126.37.171:443 ยท pagebuilder-fe-api.volleyballworld.com
2026-01-23 14:12
HTTP/1.1 200 OK Content-Type: text/html Strict-Transport-Security: max-age=31536000; includeSubDomains X-Akamai-Transformed: 9 45 0 pmb=mRUM,1 Cache-Control: private, max-age=300 Expires: Fri, 23 Jan 2026 14:17:28 GMT Date: Fri, 23 Jan 2026 14:12:28 GMT Content-Length: 45 Connection: close Server-Timing: cdn-cache; desc=HIT Server-Timing: edge; dur=10 Server-Timing: origin; dur=0 Access-Control-Allow-Origin: * Server-Timing: ak_p; desc="1769177548560_1753097639_60785165_1081_1481_11_16_-";dur=1 Welcome to Forge Frontend API - version 1.9.1