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: 5733ddf49ff49cd1f3d88d60d2f110e081615d2789e201ff24845cf66d5f1ebe
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths:
GET /v1/cinema/country/{country}/cinemasWithGate
GET /v1/externalbooking/externalBookingId/{id}
POST /v1/externalbooking/Privatization/ListbyCinemas
POST /v1/externalbooking/add
POST /v1/externalbooking/cinemas/{cinemaId}/cancel
POST /v1/externalbooking/externalBookingId/{Id}/delete
POST /v1/externalbooking/externalBookingId/{id}/update
POST /v1/externalbookinguser/add