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: 5733ddf49ff49cd1aad03549349faf5f61e44e379bcba3c569815b09fb4ce802
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/UsersFavorites/{id}
GET /api/AssetsResolutions
GET /api/Assortments/allowed
GET /api/Brands
GET /api/Brands/{brand}
GET /api/Countries
GET /api/Countries/{id}
GET /api/Cultures
GET /api/FileFormats
GET /api/Languages
GET /api/Packages
GET /api/Packages/self
GET /api/Packages/{packageId}
GET /api/Products/{reference}
GET /api/Products/{reference}/preview
GET /api/Roles/allowed
GET /api/Roles/self
GET /api/Users/logout
GET /api/Users/self
GET /api/Users/{id}
GET /api/UsersCarts/copy
GET /api/UsersCarts/self
GET /api/UsersFavorites
GET /api/flush
GET /api/info/autherror
GET /api/info/error
GET /api/sendmail
POST /api/Products/copy
POST /api/Products/notfound
POST /api/Products/search
POST /api/Users
POST /api/Users/search
POST /api/UsersCarts
POST /api/UsersCarts/all
PUT /api/Users/block/{email}
PUT /api/Users/self/legal
PUT /api/Users/unblock/{email}
Open service 18.198.195.36:443 ยท extranet-api.dev.richemontpartners.com
2025-12-22 09:57
HTTP/1.1 200 OK Cache-Control: no-store, no-cache Pragma: no-cache Content-Type: text/plain Expires: Thu, 01 Jan 1970 00:00:00 GMT ServerRic: sapp00026 X-Frame-Options: SAMEORIGIN X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff Strict-Transport-Security: max-age=16070400 Content-Security-Policy: https: Referrer-Policy: no-referrer Date: Mon, 22 Dec 2025 09:57:58 GMT Connection: close Transfer-Encoding: chunked Healthy