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: 5733ddf49ff49cd1aad035495c6eea06deb664e4c465cf38439521098619ec80
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /Analysis/All
GET /Analysis/{itemId}
GET /Analysis/{itemId}/GetForEdit
GET /AnalysisArticle/All
GET /AnalysisArticle/{itemId}
GET /AnalysisArticle/{itemId}/GetForEdit
GET /AnalysisCylinder/All
GET /AnalysisCylinder/{itemId}
GET /AnalysisCylinder/{itemId}/GetForEdit
GET /Article/All
GET /Article/{itemId}
GET /Article/{itemId}/GetForEdit
GET /Collect/All
GET /Collect/{itemId}
GET /Collect/{itemId}/GetForEdit
GET /CollectCylinder/All
GET /CollectCylinder/{itemId}
GET /CollectCylinder/{itemId}/GetForEdit
GET /Customer/All
GET /Customer/{itemId}
GET /Customer/{itemId}/GetForEdit
GET /CustomerAddress/All
GET /CustomerAddress/{itemId}
GET /CustomerAddress/{itemId}/GetForEdit
GET /Cylinder/All
GET /Cylinder/CylinderByCode
GET /Cylinder/CylinderMaxCycle
GET /Cylinder/{itemId}
GET /Cylinder/{itemId}/GetForEdit
GET /Delivery/All
GET /Delivery/{itemId}
GET /Delivery/{itemId}/GetForEdit
GET /DeliveryCylinder/All
GET /DeliveryCylinder/{itemId}
GET /DeliveryCylinder/{itemId}/GetForEdit
GET /Department/All
GET /Department/{itemId}
GET /Department/{itemId}/GetForEdit
GET /Init/All
GET /Init/{itemId}
GET /Init/{itemId}/GetForEdit
GET /InitTon/All
GET /InitTon/{itemId}
GET /InitTon/{itemId}/GetForEdit
GET /Login
GET /ProcessingCode/All
GET /ProcessingCode/{itemId}
GET /ProcessingCode/{itemId}/GetForEdit
GET /Producer/All
GET /Producer/{itemId}
GET /Producer/{itemId}/GetForEdit
GET /Profile/All
GET /Profile/{itemId}
GET /Profile/{itemId}/GetForEdit
GET /Refurbishment/All
GET /Refurbishment/{itemId}
GET /Refurbishment/{itemId}/GetForEdit
GET /RefurbishmentCylinder/All
GET /RefurbishmentCylinder/{itemId}
GET /RefurbishmentCylinder/{itemId}/GetForEdit
GET /Reuse/All
GET /Reuse/{itemId}
GET /Reuse/{itemId}/GetForEdit
GET /ReuseTon/All
GET /ReuseTon/{itemId}
GET /ReuseTon/{itemId}/GetForEdit
GET /Sending/All
GET /Sending/{itemId}
GET /Sending/{itemId}/GetForEdit
GET /SendingTon/All
GET /SendingTon/{itemId}
GET /SendingTon/{itemId}/GetForEdit
GET /Shutdown/All
GET /Shutdown/{itemId}
GET /Shutdown/{itemId}/GetForEdit
GET /ShutdownTon/All
GET /ShutdownTon/{itemId}
GET /ShutdownTon/{itemId}/GetForEdit
GET /Ton/All
GET /Ton/TonByCode
GET /Ton/{itemId}
GET /Ton/{itemId}/GetForEdit
GET /User/All
GET /User/{itemId}
GET /User/{itemId}/GetForEdit
GET /UserProfile/All
GET /UserProfile/{itemId}
GET /UserProfile/{itemId}/GetForEdit
GET /WasteStream/All
GET /WasteStream/{itemId}
GET /WasteStream/{itemId}/GetForEdit
POST /Analysis
POST /Analysis/GetByQuerySpecification
POST /Analysis/Validate
POST /AnalysisArticle
POST /AnalysisArticle/GetByQuerySpecification
POST /AnalysisArticle/Validate
POST /AnalysisCylinder
POST /AnalysisCylinder/GetByQuerySpecification
POST /AnalysisCylinder/Validate
POST /Article
POST /Article/GetByQuerySpecification
POST /Article/Validate
POST /Collect
POST /Collect/GetByQuerySpecification
POST /Collect/Validate
POST /CollectCylinder
POST /CollectCylinder/GetByQuerySpecification
POST /CollectCylinder/Validate
POST /Customer
POST /Customer/GetByQuerySpecification
POST /Customer/Validate
POST /CustomerAddress
POST /CustomerAddress/GetByQuerySpecification
POST /CustomerAddress/Validate
POST /Cylinder
POST /Cylinder/GetByQuerySpecification
POST /Cylinder/Validate
POST /Delivery
POST /Delivery/GetByQuerySpecification
POST /Delivery/Validate
POST /DeliveryCylinder
POST /DeliveryCylinder/GetByQuerySpecification
POST /DeliveryCylinder/Validate
POST /Department
POST /Department/GetByQuerySpecification
POST /Department/Validate
POST /Init
POST /Init/GetByQuerySpecification
POST /Init/Validate
POST /InitTon
POST /InitTon/GetByQuerySpecification
POST /InitTon/Validate
POST /ProcessingCode
POST /ProcessingCode/GetByQuerySpecification
POST /ProcessingCode/Validate
POST /Producer
POST /Producer/GetByQuerySpecification
POST /Producer/Validate
POST /Profile
POST /Profile/GetByQuerySpecification
POST /Profile/Validate
POST /Refurbishment
POST /Refurbishment/GetByQuerySpecification
POST /Refurbishment/Validate
POST /RefurbishmentCylinder
POST /RefurbishmentCylinder/GetByQuerySpecification
POST /RefurbishmentCylinder/Validate
POST /Reuse
POST /Reuse/GetByQuerySpecification
POST /Reuse/Validate
POST /ReuseTon
POST /ReuseTon/GetByQuerySpecification
POST /ReuseTon/Validate
POST /Sending
POST /Sending/GetByQuerySpecification
POST /Sending/Validate
POST /SendingTon
POST /SendingTon/GetByQuerySpecification
POST /SendingTon/Validate
POST /Shutdown
POST /Shutdown/GetByQuerySpecification
POST /Shutdown/Validate
POST /ShutdownTon
POST /ShutdownTon/GetByQuerySpecification
POST /ShutdownTon/Validate
POST /Ton
POST /Ton/GetByQuerySpecification
POST /Ton/Validate
POST /User
POST /User/GetByQuerySpecification
POST /User/Validate
POST /UserProfile
POST /UserProfile/GetByQuerySpecification
POST /UserProfile/Validate
POST /WasteStream
POST /WasteStream/GetByQuerySpecification
POST /WasteStream/Validate
PUT /Analysis/Update
PUT /AnalysisArticle/Update
PUT /AnalysisCylinder/Update
PUT /Article/Update
PUT /Collect/Update
PUT /CollectCylinder/Update
PUT /Customer/Update
PUT /CustomerAddress/Update
PUT /Cylinder/Update
PUT /Delivery/Update
PUT /DeliveryCylinder/Update
PUT /Department/Update
PUT /Init/Update
PUT /InitTon/Update
PUT /ProcessingCode/Update
PUT /Producer/Update
PUT /Profile/Update
PUT /Refurbishment/Update
PUT /RefurbishmentCylinder/Update
PUT /Reuse/Update
PUT /ReuseTon/Update
PUT /Sending/Update
PUT /SendingTon/Update
PUT /Shutdown/Update
PUT /ShutdownTon/Update
PUT /Ton/Update
PUT /User/Update
PUT /UserProfile/Update
PUT /WasteStream/Update
Severity: info
Fingerprint: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Severity: info
Fingerprint: 5733ddf49ff49cd1f3d88d60b3735f41c7eb18d39178f98922c9a8fcebbbf37d
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths:
GET /Analysis/All
GET /Analysis/{itemId}
GET /Analysis/{itemId}/GetForEdit
GET /AnalysisArticle/All
GET /AnalysisArticle/{itemId}
GET /AnalysisArticle/{itemId}/GetForEdit
GET /AnalysisCylinder/All
GET /AnalysisCylinder/{itemId}
GET /AnalysisCylinder/{itemId}/GetForEdit
GET /Article/All
GET /Article/{itemId}
GET /Article/{itemId}/GetForEdit
GET /Collect/All
GET /Collect/{itemId}
GET /Collect/{itemId}/GetForEdit
GET /CollectCylinder/All
GET /CollectCylinder/{itemId}
GET /CollectCylinder/{itemId}/GetForEdit
GET /Customer/All
GET /Customer/{itemId}
GET /Customer/{itemId}/GetForEdit
GET /CustomerAddress/All
GET /CustomerAddress/{itemId}
GET /CustomerAddress/{itemId}/GetForEdit
GET /Cylinder/All
GET /Cylinder/CylinderByCode
GET /Cylinder/CylinderMaxCycle
GET /Cylinder/{itemId}
GET /Cylinder/{itemId}/GetForEdit
GET /Delivery/All
GET /Delivery/{itemId}
GET /Delivery/{itemId}/GetForEdit
GET /DeliveryCylinder/All
GET /DeliveryCylinder/{itemId}
GET /DeliveryCylinder/{itemId}/GetForEdit
GET /Department/All
GET /Department/{itemId}
GET /Department/{itemId}/GetForEdit
GET /Init/All
GET /Init/{itemId}
GET /Init/{itemId}/GetForEdit
GET /InitTon/All
GET /InitTon/{itemId}
GET /InitTon/{itemId}/GetForEdit
GET /Login
GET /ProcessingCode/All
GET /ProcessingCode/{itemId}
GET /ProcessingCode/{itemId}/GetForEdit
GET /Producer/All
GET /Producer/{itemId}
GET /Producer/{itemId}/GetForEdit
GET /Profile/All
GET /Profile/{itemId}
GET /Profile/{itemId}/GetForEdit
GET /Refurbishment/All
GET /Refurbishment/{itemId}
GET /Refurbishment/{itemId}/GetForEdit
GET /RefurbishmentCylinder/All
GET /RefurbishmentCylinder/{itemId}
GET /RefurbishmentCylinder/{itemId}/GetForEdit
GET /Reuse/All
GET /Reuse/{itemId}
GET /Reuse/{itemId}/GetForEdit
GET /ReuseTon/All
GET /ReuseTon/{itemId}
GET /ReuseTon/{itemId}/GetForEdit
GET /Sending/All
GET /Sending/{itemId}
GET /Sending/{itemId}/GetForEdit
GET /SendingTon/All
GET /SendingTon/{itemId}
GET /SendingTon/{itemId}/GetForEdit
GET /Shutdown/All
GET /Shutdown/{itemId}
GET /Shutdown/{itemId}/GetForEdit
GET /ShutdownTon/All
GET /ShutdownTon/{itemId}
GET /ShutdownTon/{itemId}/GetForEdit
GET /Ton/All
GET /Ton/TonByCode
GET /Ton/{itemId}
GET /Ton/{itemId}/GetForEdit
GET /User/All
GET /User/{itemId}
GET /User/{itemId}/GetForEdit
GET /UserProfile/All
GET /UserProfile/{itemId}
GET /UserProfile/{itemId}/GetForEdit
GET /WasteStream/All
GET /WasteStream/{itemId}
GET /WasteStream/{itemId}/GetForEdit
POST /Analysis
POST /Analysis/GetByQuerySpecification
POST /Analysis/Validate
POST /AnalysisArticle
POST /AnalysisArticle/GetByQuerySpecification
POST /AnalysisArticle/Validate
POST /AnalysisCylinder
POST /AnalysisCylinder/GetByQuerySpecification
POST /AnalysisCylinder/Validate
POST /Article
POST /Article/GetByQuerySpecification
POST /Article/Validate
POST /Collect
POST /Collect/GetByQuerySpecification
POST /Collect/Validate
POST /CollectCylinder
POST /CollectCylinder/GetByQuerySpecification
POST /CollectCylinder/Validate
POST /Customer
POST /Customer/GetByQuerySpecification
POST /Customer/Validate
POST /CustomerAddress
POST /CustomerAddress/GetByQuerySpecification
POST /CustomerAddress/Validate
POST /Cylinder
POST /Cylinder/GetByQuerySpecification
POST /Cylinder/Validate
POST /Delivery
POST /Delivery/GetByQuerySpecification
POST /Delivery/Validate
POST /DeliveryCylinder
POST /DeliveryCylinder/GetByQuerySpecification
POST /DeliveryCylinder/Validate
POST /Department
POST /Department/GetByQuerySpecification
POST /Department/Validate
POST /Init
POST /Init/GetByQuerySpecification
POST /Init/Validate
POST /InitTon
POST /InitTon/GetByQuerySpecification
POST /InitTon/Validate
POST /ProcessingCode
POST /ProcessingCode/GetByQuerySpecification
POST /ProcessingCode/Validate
POST /Producer
POST /Producer/GetByQuerySpecification
POST /Producer/Validate
POST /Profile
POST /Profile/GetByQuerySpecification
POST /Profile/Validate
POST /Refurbishment
POST /Refurbishment/GetByQuerySpecification
POST /Refurbishment/Validate
POST /RefurbishmentCylinder
POST /RefurbishmentCylinder/GetByQuerySpecification
POST /RefurbishmentCylinder/Validate
POST /Reuse
POST /Reuse/GetByQuerySpecification
POST /Reuse/Validate
POST /ReuseTon
POST /ReuseTon/GetByQuerySpecification
POST /ReuseTon/Validate
POST /Sending
POST /Sending/GetByQuerySpecification
POST /Sending/Validate
POST /SendingTon
POST /SendingTon/GetByQuerySpecification
POST /SendingTon/Validate
POST /Shutdown
POST /Shutdown/GetByQuerySpecification
POST /Shutdown/Validate
POST /ShutdownTon
POST /ShutdownTon/GetByQuerySpecification
POST /ShutdownTon/Validate
POST /Ton
POST /Ton/GetByQuerySpecification
POST /Ton/Validate
POST /User
POST /User/GetByQuerySpecification
POST /User/Validate
POST /UserProfile
POST /UserProfile/GetByQuerySpecification
POST /UserProfile/Validate
POST /WasteStream
POST /WasteStream/GetByQuerySpecification
POST /WasteStream/Validate
PUT /Analysis/Update
PUT /AnalysisArticle/Update
PUT /AnalysisCylinder/Update
PUT /Article/Update
PUT /Collect/Update
PUT /CollectCylinder/Update
PUT /Customer/Update
PUT /CustomerAddress/Update
PUT /Cylinder/Update
PUT /Delivery/Update
PUT /DeliveryCylinder/Update
PUT /Department/Update
PUT /Init/Update
PUT /InitTon/Update
PUT /ProcessingCode/Update
PUT /Producer/Update
PUT /Profile/Update
PUT /Refurbishment/Update
PUT /RefurbishmentCylinder/Update
PUT /Reuse/Update
PUT /ReuseTon/Update
PUT /Sending/Update
PUT /SendingTon/Update
PUT /Shutdown/Update
PUT /ShutdownTon/Update
PUT /Ton/Update
PUT /User/Update
PUT /UserProfile/Update
PUT /WasteStream/Update
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: 5733ddf49ff49cd1aad035495c6eea06deb664e4c465cf38439521098619ec80
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /Analysis/All
GET /Analysis/{itemId}
GET /Analysis/{itemId}/GetForEdit
GET /AnalysisArticle/All
GET /AnalysisArticle/{itemId}
GET /AnalysisArticle/{itemId}/GetForEdit
GET /AnalysisCylinder/All
GET /AnalysisCylinder/{itemId}
GET /AnalysisCylinder/{itemId}/GetForEdit
GET /Article/All
GET /Article/{itemId}
GET /Article/{itemId}/GetForEdit
GET /Collect/All
GET /Collect/{itemId}
GET /Collect/{itemId}/GetForEdit
GET /CollectCylinder/All
GET /CollectCylinder/{itemId}
GET /CollectCylinder/{itemId}/GetForEdit
GET /Customer/All
GET /Customer/{itemId}
GET /Customer/{itemId}/GetForEdit
GET /CustomerAddress/All
GET /CustomerAddress/{itemId}
GET /CustomerAddress/{itemId}/GetForEdit
GET /Cylinder/All
GET /Cylinder/CylinderByCode
GET /Cylinder/CylinderMaxCycle
GET /Cylinder/{itemId}
GET /Cylinder/{itemId}/GetForEdit
GET /Delivery/All
GET /Delivery/{itemId}
GET /Delivery/{itemId}/GetForEdit
GET /DeliveryCylinder/All
GET /DeliveryCylinder/{itemId}
GET /DeliveryCylinder/{itemId}/GetForEdit
GET /Department/All
GET /Department/{itemId}
GET /Department/{itemId}/GetForEdit
GET /Init/All
GET /Init/{itemId}
GET /Init/{itemId}/GetForEdit
GET /InitTon/All
GET /InitTon/{itemId}
GET /InitTon/{itemId}/GetForEdit
GET /Login
GET /ProcessingCode/All
GET /ProcessingCode/{itemId}
GET /ProcessingCode/{itemId}/GetForEdit
GET /Producer/All
GET /Producer/{itemId}
GET /Producer/{itemId}/GetForEdit
GET /Profile/All
GET /Profile/{itemId}
GET /Profile/{itemId}/GetForEdit
GET /Refurbishment/All
GET /Refurbishment/{itemId}
GET /Refurbishment/{itemId}/GetForEdit
GET /RefurbishmentCylinder/All
GET /RefurbishmentCylinder/{itemId}
GET /RefurbishmentCylinder/{itemId}/GetForEdit
GET /Reuse/All
GET /Reuse/{itemId}
GET /Reuse/{itemId}/GetForEdit
GET /ReuseTon/All
GET /ReuseTon/{itemId}
GET /ReuseTon/{itemId}/GetForEdit
GET /Sending/All
GET /Sending/{itemId}
GET /Sending/{itemId}/GetForEdit
GET /SendingTon/All
GET /SendingTon/{itemId}
GET /SendingTon/{itemId}/GetForEdit
GET /Shutdown/All
GET /Shutdown/{itemId}
GET /Shutdown/{itemId}/GetForEdit
GET /ShutdownTon/All
GET /ShutdownTon/{itemId}
GET /ShutdownTon/{itemId}/GetForEdit
GET /Ton/All
GET /Ton/TonByCode
GET /Ton/{itemId}
GET /Ton/{itemId}/GetForEdit
GET /User/All
GET /User/{itemId}
GET /User/{itemId}/GetForEdit
GET /UserProfile/All
GET /UserProfile/{itemId}
GET /UserProfile/{itemId}/GetForEdit
GET /WasteStream/All
GET /WasteStream/{itemId}
GET /WasteStream/{itemId}/GetForEdit
POST /Analysis
POST /Analysis/GetByQuerySpecification
POST /Analysis/Validate
POST /AnalysisArticle
POST /AnalysisArticle/GetByQuerySpecification
POST /AnalysisArticle/Validate
POST /AnalysisCylinder
POST /AnalysisCylinder/GetByQuerySpecification
POST /AnalysisCylinder/Validate
POST /Article
POST /Article/GetByQuerySpecification
POST /Article/Validate
POST /Collect
POST /Collect/GetByQuerySpecification
POST /Collect/Validate
POST /CollectCylinder
POST /CollectCylinder/GetByQuerySpecification
POST /CollectCylinder/Validate
POST /Customer
POST /Customer/GetByQuerySpecification
POST /Customer/Validate
POST /CustomerAddress
POST /CustomerAddress/GetByQuerySpecification
POST /CustomerAddress/Validate
POST /Cylinder
POST /Cylinder/GetByQuerySpecification
POST /Cylinder/Validate
POST /Delivery
POST /Delivery/GetByQuerySpecification
POST /Delivery/Validate
POST /DeliveryCylinder
POST /DeliveryCylinder/GetByQuerySpecification
POST /DeliveryCylinder/Validate
POST /Department
POST /Department/GetByQuerySpecification
POST /Department/Validate
POST /Init
POST /Init/GetByQuerySpecification
POST /Init/Validate
POST /InitTon
POST /InitTon/GetByQuerySpecification
POST /InitTon/Validate
POST /ProcessingCode
POST /ProcessingCode/GetByQuerySpecification
POST /ProcessingCode/Validate
POST /Producer
POST /Producer/GetByQuerySpecification
POST /Producer/Validate
POST /Profile
POST /Profile/GetByQuerySpecification
POST /Profile/Validate
POST /Refurbishment
POST /Refurbishment/GetByQuerySpecification
POST /Refurbishment/Validate
POST /RefurbishmentCylinder
POST /RefurbishmentCylinder/GetByQuerySpecification
POST /RefurbishmentCylinder/Validate
POST /Reuse
POST /Reuse/GetByQuerySpecification
POST /Reuse/Validate
POST /ReuseTon
POST /ReuseTon/GetByQuerySpecification
POST /ReuseTon/Validate
POST /Sending
POST /Sending/GetByQuerySpecification
POST /Sending/Validate
POST /SendingTon
POST /SendingTon/GetByQuerySpecification
POST /SendingTon/Validate
POST /Shutdown
POST /Shutdown/GetByQuerySpecification
POST /Shutdown/Validate
POST /ShutdownTon
POST /ShutdownTon/GetByQuerySpecification
POST /ShutdownTon/Validate
POST /Ton
POST /Ton/GetByQuerySpecification
POST /Ton/Validate
POST /User
POST /User/GetByQuerySpecification
POST /User/Validate
POST /UserProfile
POST /UserProfile/GetByQuerySpecification
POST /UserProfile/Validate
POST /WasteStream
POST /WasteStream/GetByQuerySpecification
POST /WasteStream/Validate
PUT /Analysis/Update
PUT /AnalysisArticle/Update
PUT /AnalysisCylinder/Update
PUT /Article/Update
PUT /Collect/Update
PUT /CollectCylinder/Update
PUT /Customer/Update
PUT /CustomerAddress/Update
PUT /Cylinder/Update
PUT /Delivery/Update
PUT /DeliveryCylinder/Update
PUT /Department/Update
PUT /Init/Update
PUT /InitTon/Update
PUT /ProcessingCode/Update
PUT /Producer/Update
PUT /Profile/Update
PUT /Refurbishment/Update
PUT /RefurbishmentCylinder/Update
PUT /Reuse/Update
PUT /ReuseTon/Update
PUT /Sending/Update
PUT /SendingTon/Update
PUT /Shutdown/Update
PUT /ShutdownTon/Update
PUT /Ton/Update
PUT /User/Update
PUT /UserProfile/Update
PUT /WasteStream/Update
The following URL (usually /.git/config) is publicly accessible and is leaking source code and repository configuration.
Severity: medium
Fingerprint: 2580fa947178c88602b1737db148c044b81b03713d63bb82370a6522a5dc45ee
[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = /var/www/test.potier.cloud fetch = +refs/heads/*:refs/remotes/origin/*
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: 5733ddf49ff49cd110a331ecc360aa697b9c9efe97113b06101f041acc89b890
Public Swagger UI/API detected at path: /v2/api-docs - sample paths:
DELETE /api/onboarding/bo/card_choice_delete
DELETE /api/onboarding/bo/delete_role
DELETE /api/onboarding/bo/delete_user
DELETE /api/onboarding/bo/product_choice_delete
GET /api/onboarding/activation_capture
GET /api/onboarding/agent_monitoring
GET /api/onboarding/bo/all_user_data
GET /api/onboarding/bo/card_choice_get_all
GET /api/onboarding/bo/card_choice_get_one
GET /api/onboarding/bo/check_iam_health
GET /api/onboarding/bo/cities
GET /api/onboarding/bo/data_id_toc
GET /api/onboarding/bo/data_opening_account
GET /api/onboarding/bo/districts
GET /api/onboarding/bo/dual-control/approvals
GET /api/onboarding/bo/dual-control/card/{idCard}
GET /api/onboarding/bo/dual-control/city/{idCity}
GET /api/onboarding/bo/dual-control/content/{idToc}
GET /api/onboarding/bo/dual-control/district/{idDistrict}
GET /api/onboarding/bo/dual-control/group/{idGroup}
GET /api/onboarding/bo/dual-control/mandatory-field/{idMandatoryField}
GET /api/onboarding/bo/dual-control/marketing-code/{idMarketing}
GET /api/onboarding/bo/dual-control/menus
GET /api/onboarding/bo/dual-control/occupation-mapping/{idOccupationMapping}
GET /api/onboarding/bo/dual-control/operational-hour/{idOperational}
GET /api/onboarding/bo/dual-control/position-mapping/{idPositionMapping}
GET /api/onboarding/bo/dual-control/postal-code-branch-number/{idPCBN}
GET /api/onboarding/bo/dual-control/product/{idProduct}
GET /api/onboarding/bo/dual-control/province/{idProvince}
GET /api/onboarding/bo/dual-control/roles
GET /api/onboarding/bo/dual-control/stock-mapping/{idStockMapping}
GET /api/onboarding/bo/dual-control/sub-district/{idSubDistrict}
GET /api/onboarding/bo/dual-control/user/{idUser}
GET /api/onboarding/bo/get_all_menu
GET /api/onboarding/bo/get_all_menu_by_role
GET /api/onboarding/bo/get_all_role
GET /api/onboarding/bo/get_file_type
GET /api/onboarding/bo/get_menu
GET /api/onboarding/bo/get_operational_hour
GET /api/onboarding/bo/group/{idGroup}
GET /api/onboarding/bo/groups
GET /api/onboarding/bo/login_external
GET /api/onboarding/bo/logout
GET /api/onboarding/bo/mapping_source
GET /api/onboarding/bo/marketing_code_get_all
GET /api/onboarding/bo/marketing_code_get_one
GET /api/onboarding/bo/menu_management_list
GET /api/onboarding/bo/parameter-limit
GET /api/onboarding/bo/product_choice_get_all
GET /api/onboarding/bo/product_choice_get_one
GET /api/onboarding/bo/provinces
GET /api/onboarding/bo/referal_code_data
GET /api/onboarding/bo/session_retry_process
GET /api/onboarding/bo/session_retry_status
GET /api/onboarding/bo/subDistricts
GET /api/onboarding/bo/toc_get_all
GET /api/onboarding/bo/toc_get_one
GET /api/onboarding/bo/users
GET /api/onboarding/bo/users/{userId}
GET /api/onboarding/cisco-session
GET /api/onboarding/data_company_field
GET /api/onboarding/data_debit_card_detail
GET /api/onboarding/data_mail_delivery_code
GET /api/onboarding/data_occupation
GET /api/onboarding/data_position
GET /api/onboarding/data_relationship
GET /api/onboarding/data_source_of_income
GET /api/onboarding/debit_card_resend_otp
GET /api/onboarding/generate_call_ref
GET /api/onboarding/get_all_data_education
GET /api/onboarding/get_all_data_objective
GET /api/onboarding/get_all_data_reject_category
GET /api/onboarding/get_all_data_religion
GET /api/onboarding/get_data_form_request
GET /api/onboarding/get_data_ktp
GET /api/onboarding/get_data_npwp
GET /api/onboarding/get_data_old_debit_card
GET /api/onboarding/get_data_selfie
GET /api/onboarding/get_data_signature
GET /api/onboarding/get_mpin_public_key
GET /api/onboarding/get_operational_hour
GET /api/onboarding/get_privy_number
GET /api/onboarding/get_ref2
GET /api/onboarding/get_state
GET /api/onboarding/inquiry-partner
GET /api/onboarding/partner
GET /api/onboarding/public_data/browser-version
GET /api/onboarding/public_data/card_choice
GET /api/onboarding/public_data/city
GET /api/onboarding/public_data/data_cobrand
GET /api/onboarding/public_data/data_education
GET /api/onboarding/public_data/data_objective
GET /api/onboarding/public_data/data_qrdomain
GET /api/onboarding/public_data/data_religion
GET /api/onboarding/public_data/data_stock
GET /api/onboarding/public_data/dati2
GET /api/onboarding/public_data/images/card_choice/{fileName}
GET /api/onboarding/public_data/images/product_choice/{fileName}
GET /api/onboarding/public_data/kelurahan
GET /api/onboarding/public_data/location
GET /api/onboarding/public_data/mandiri-livin-url
GET /api/onboarding/public_data/menu-card-replacement
GET /api/onboarding/public_data/preparation_instruction
GET /api/onboarding/public_data/priority_number_product_choice_insert
GET /api/onboarding/public_data/priority_number_product_choice_update
GET /api/onboarding/public_data/product_choice
GET /api/onboarding/public_data/province
GET /api/onboarding/public_data/sub-menu-lainnya
GET /api/onboarding/public_data/sub_district
GET /api/onboarding/public_data/toc
GET /api/onboarding/public_data/validate_marketing_code
GET /api/onboarding/public_data/validate_ref
GET /api/onboarding/public_key
GET /api/onboarding/qrcode/hit/{shortLink}
GET /api/onboarding/qrcode/image
GET /api/onboarding/referral-product
GET /api/onboarding/resend_otp
GET /api/onboarding/resume_resend_otp
GET /api/onboarding/reupload_documentum
GET /api/onboarding/start-kyc
POST /api/onboarding/bo/card_choice_insert
POST /api/onboarding/bo/card_choice_update
POST /api/onboarding/bo/change_password
POST /api/onboarding/bo/cif_info
POST /api/onboarding/bo/city
POST /api/onboarding/bo/create_role
POST /api/onboarding/bo/district
POST /api/onboarding/bo/download_investor_excel
POST /api/onboarding/bo/download_investor_pdf
POST /api/onboarding/bo/download_parameter
POST /api/onboarding/bo/download_report
POST /api/onboarding/bo/end_session
POST /api/onboarding/bo/group
POST /api/onboarding/bo/login
POST /api/onboarding/bo/marketing_code_insert
POST /api/onboarding/bo/marketing_code_insert_bulk
POST /api/onboarding/bo/product_choice_insert
POST /api/onboarding/bo/product_choice_update
POST /api/onboarding/bo/province
POST /api/onboarding/bo/register
POST /api/onboarding/bo/reset_password
POST /api/onboarding/bo/reset_password_request
POST /api/onboarding/bo/session_status
POST /api/onboarding/bo/subDistrict
POST /api/onboarding/bo/update_operational_hour
POST /api/onboarding/bo/update_role
POST /api/onboarding/bo/update_role_menu
POST /api/onboarding/bo/upload_documentum
POST /api/onboarding/bo/upload_investor
POST /api/onboarding/bo/upload_parameter
POST /api/onboarding/change_privy_mobile_number
POST /api/onboarding/confirm_request_resume
POST /api/onboarding/confirm_start
POST /api/onboarding/debit-card/old
POST /api/onboarding/debit-card/upload
POST /api/onboarding/input_bo_exist
POST /api/onboarding/input_bo_new
POST /api/onboarding/input_pin_etb
POST /api/onboarding/inquiry_bo
POST /api/onboarding/privy_otp_resend
POST /api/onboarding/public_data/check_browser_compability
POST /api/onboarding/public_data/unshorten_url
POST /api/onboarding/qrcode/unshorten
POST /api/onboarding/request_resume
POST /api/onboarding/session_retry_process
POST /api/onboarding/start
POST /api/onboarding/submit_debitcard_activation
POST /api/onboarding/submit_debitcard_otp_confirmation
POST /api/onboarding/submit_debitcard_pin
POST /api/onboarding/submit_debitcard_validation
POST /api/onboarding/submit_form
POST /api/onboarding/submit_mpin
POST /api/onboarding/submit_preview
POST /api/onboarding/submit_privy_otp
POST /api/onboarding/submit_privy_toc_response
POST /api/onboarding/upload_capture
POST /api/onboarding/upload_ktp
POST /api/onboarding/upload_npwp
POST /api/onboarding/upload_selfie
POST /api/onboarding/upload_signature_specimen
PUT /api/onboarding/bo/city/{cityId}
PUT /api/onboarding/bo/district/{districtId}
PUT /api/onboarding/bo/dual-control/approve
PUT /api/onboarding/bo/dual-control/reject
PUT /api/onboarding/bo/mapping_source_update
PUT /api/onboarding/bo/marketing_code_update/{marketingCode}
PUT /api/onboarding/bo/province/{provinceId}
PUT /api/onboarding/bo/subDistrict/{subDistrictId}
PUT /api/onboarding/bo/toc_update
PUT /api/onboarding/bo/update_authority_user
PUT /api/onboarding/card-replacement/input_card_address
PUT /api/onboarding/create_account
PUT /api/onboarding/input-check-balance
PUT /api/onboarding/input_card_address
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: 5733ddf49ff49cd1aad035490abfcea7617c0ef4b7a268c580530306d9560627
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/data/batch-delete
DELETE /api/data/delete
GET /api/common/area
GET /api/common/city
GET /api/common/download
GET /api/common/picklist
GET /api/contact/detail
GET /api/contract/approval/overview
GET /api/contract/check/payer/bank
GET /api/contract/detail
GET /api/contract/mm/detail
GET /api/contract/mpg/price
GET /api/contract/pkg/price
GET /api/contract/product/detail
GET /api/customer/price/info
GET /api/customer/shipto/receive/contact/list
GET /api/data/download/{entityName}/{entityId}/{fileAttribute}
GET /api/home/toducount
GET /api/pipo/{path}
GET /api/pkg/pkg-doa
GET /api/qixinbao/adv-search
GET /api/qixinbao/authorize
GET /api/qixinbao/get-basic-info
GET /api/qixinbao/get-company-detail
GET /api/qixinbao/get-credit-score
GET /api/user/info
GET /auth
GET /token
POST /api/common/setting
POST /api/contact/create
POST /api/contact/edit
POST /api/contact/invalid
POST /api/contact/list
POST /api/contract/approval/addsigner
POST /api/contract/approval/commit
POST /api/contract/approval/pass
POST /api/contract/approval/reject
POST /api/contract/edit
POST /api/contract/gas/price/add
POST /api/contract/gas/price/edit
POST /api/contract/list
POST /api/contract/mm/calc
POST /api/contract/product/detail/edit
POST /api/contract/renewal
POST /api/contract/rent/price/add
POST /api/contract/rent/price/edit
POST /api/contract/send/file
POST /api/contract/tank/add
POST /api/contract/tank/edit
POST /api/contract/temp/check
POST /api/contract/temp/fill
POST /api/contract/temp/match
POST /api/contract/upload/fail/continue
POST /api/contract/vmi/price/add
POST /api/contract/vmi/price/edit
POST /api/customer/billto/list
POST /api/customer/payer/bank/edit
POST /api/customer/payer/list
POST /api/data/add
POST /api/data/execute
POST /api/data/form
POST /api/data/list
POST /api/data/update
POST /api/data/upload/{entityName}/{entityId}/{fileAttribute}
POST /api/data/view
POST /api/displan/batch/reject
POST /api/displan/sourcesfactory
POST /api/displan/submit
POST /api/home/todo/contract
POST /api/home/todo/displan
POST /api/home/todo/renewal/contract
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: 5733ddf49ff49cd1aad035492586d5538062531b2c5805a7c3751c18b6a602f7
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /v1/bucket/image/bucketurl
GET /v1/bucket/image/{imageKey}
GET /v1/bucket/image/{imageKey}/{size}
GET /v1/bucket/image/{prefix}/{imageKey}/{size}
PUT /v1/bucket/image
PUT /v1/bucket/image/raw
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: 5733ddf49ff49cd1aad035490abfcea7617c0ef4b7a268c580530306d9560627
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/data/batch-delete
DELETE /api/data/delete
GET /api/common/area
GET /api/common/city
GET /api/common/download
GET /api/common/picklist
GET /api/contact/detail
GET /api/contract/approval/overview
GET /api/contract/check/payer/bank
GET /api/contract/detail
GET /api/contract/mm/detail
GET /api/contract/mpg/price
GET /api/contract/pkg/price
GET /api/contract/product/detail
GET /api/customer/price/info
GET /api/customer/shipto/receive/contact/list
GET /api/data/download/{entityName}/{entityId}/{fileAttribute}
GET /api/home/toducount
GET /api/pipo/{path}
GET /api/pkg/pkg-doa
GET /api/qixinbao/adv-search
GET /api/qixinbao/authorize
GET /api/qixinbao/get-basic-info
GET /api/qixinbao/get-company-detail
GET /api/qixinbao/get-credit-score
GET /api/user/info
GET /auth
GET /token
POST /api/common/setting
POST /api/contact/create
POST /api/contact/edit
POST /api/contact/invalid
POST /api/contact/list
POST /api/contract/approval/addsigner
POST /api/contract/approval/commit
POST /api/contract/approval/pass
POST /api/contract/approval/reject
POST /api/contract/edit
POST /api/contract/gas/price/add
POST /api/contract/gas/price/edit
POST /api/contract/list
POST /api/contract/mm/calc
POST /api/contract/product/detail/edit
POST /api/contract/renewal
POST /api/contract/rent/price/add
POST /api/contract/rent/price/edit
POST /api/contract/send/file
POST /api/contract/tank/add
POST /api/contract/tank/edit
POST /api/contract/temp/check
POST /api/contract/temp/fill
POST /api/contract/temp/match
POST /api/contract/upload/fail/continue
POST /api/contract/vmi/price/add
POST /api/contract/vmi/price/edit
POST /api/customer/billto/list
POST /api/customer/payer/bank/edit
POST /api/customer/payer/list
POST /api/data/add
POST /api/data/execute
POST /api/data/form
POST /api/data/list
POST /api/data/update
POST /api/data/upload/{entityName}/{entityId}/{fileAttribute}
POST /api/data/view
POST /api/displan/batch/reject
POST /api/displan/sourcesfactory
POST /api/displan/submit
POST /api/home/todo/contract
POST /api/home/todo/displan
POST /api/home/todo/renewal/contract
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: 5733ddf49ff49cd1926e27d0926e27d0926e27d0926e27d0926e27d0926e27d0
Public Swagger UI/API detected at path: /webjars/swagger-ui/index.html