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: 5733ddf49ff49cd1aad035491a3b826ffd58fbc1e2c5212ccc46c24fd8e73494
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/DbHealth GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/FeedbackRequestForm GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C GET /api/v1/core-ping GET /api/v1/debug/token POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/FeedbackRequestFormResponse POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826ffd58fbc1e2c5212ccc46c24fca248c8b
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/DbHealth GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/FeedbackRequestForm GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C GET /api/v1/core-ping GET /api/v1/debug/token POST /FeedbackRequestFormResponse POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient