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: 5733ddf49ff49cd1aad03549d454fe765df7f18c1cd27ff281827e6c5ef656d0
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/SpecialSchedule/Delete/{id}
GET /api/Category/GetAll
GET /api/Health
GET /api/Item/GetById/{id}
GET /api/Item/Search/{query}
GET /api/Menu/GetLastMenu
GET /api/Menu/{id}
GET /api/Order/{client}
GET /api/Parameter/GetByKey/{key}
GET /api/PaymentMethod/GetAll
GET /api/PaymentMethod/GetById/{id}
GET /api/SpecialSchedule/GetAll
GET /api/SpecialSchedule/GetByDate/{date}
GET /api/Store/GetById/{id}
GET /api/WeeklySchedule/GetAll
GET /api/WeeklySchedule/GetByDayWeek/{dayWeek}
GET /api/orders
POST /api/Menu
POST /api/Menu/Login
POST /api/Menu/Save
POST /api/Order/Create
POST /api/Parameter/Create
POST /api/PaymentMethod/Create
POST /api/SpecialSchedule/Create
POST /api/Store/Create
POST /api/User/Create
POST /api/WeeklySchedule/Create
POST /api/WeeklySchedule/GetDaySchedule
POST /api/WeeklySchedule/IsOpen
POST /api/orders_cancel/{orderId}
PUT /api/Parameter/Update
PUT /api/SpecialSchedule/Update
PUT /api/WeeklySchedule/Update
PUT /api/WeeklySchedule/UpdateAll
PUT /api/orders_update
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354974ec503f846fc37bee542e0da730b4928744b10c
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/Category/GetAll
GET /api/Health
GET /api/Item/GetById/{id}
GET /api/Item/Search/{query}
GET /api/Menu/GetLastMenu
GET /api/Menu/{id}
GET /api/Order/{client}
GET /api/Parameter/GetByKey/{key}
GET /api/PaymentMethod/GetAll
GET /api/PaymentMethod/GetById/{id}
GET /api/Store/GetById/{id}
GET /api/orders
POST /api/Menu
POST /api/Menu/Login
POST /api/Menu/Save
POST /api/Order/Create
POST /api/Parameter/Create
POST /api/PaymentMethod/Create
POST /api/Store/Create
POST /api/User/Create
POST /api/orders_cancel/{orderId}
PUT /api/Parameter/Update
PUT /api/orders_update