PatchSiren cyber security CVE debrief
CVE-2026-110607 BizSpring CVE debrief
CVE-2026-110607 is a payment verification bypass vulnerability in BizSpring Shop through commit cf22d39daaf1. An authenticated buyer can exploit this by calling the PaymentController.testPostPay handler to mark orders as paid. This allows for obtaining goods without payment or settling other members' orders. The vulnerability can be exploited by generating a payment log via /member/payment/load and requesting /member/payment/test_post_pay_{paymentLogSn}. Defenders should assess exposure, verify payment logs for suspicious activity, and restrict access to the PaymentController.testPostPay handler.
- Vendor
- BizSpring
- Product
- BizSpring Shop
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-14
- Original CVE updated
- 2026-10-14
- Advisory published
- 2026-10-14
- Advisory updated
- 2026-10-14
Who should care
Defenders responsible for BizSpring Shop or BizSpring Java Mall deployments should assess exposure and verify payment logs for suspicious activity. They should also restrict access to the PaymentController.testPostPay handler and monitor for unauthorized use.
Why it matters
CVE-2026-110607 is a payment verification bypass vulnerability in BizSpring Shop through commit cf22d39daaf1. Defenders should prioritize verifying the presence of this vulnerability in their inventory, monitoring payment logs, and restricting access to the PaymentController.testPostPay handler.
- Defenders need to verify the presence of this vulnerability in their inventory to prevent unauthorized payment bypass.
- Security teams must monitor payment logs for suspicious activity to detect potential exploitation.
- Incident response teams should be prepared to investigate and respond to potential payment bypass incidents.
- Penetration testers and vulnerability hunters may need to verify the vulnerability in specific deployments.
Technical summary
The vulnerability exists in the PaymentController.testPostPay handler of BizSpring Shop through commit cf22d39daaf1. An authenticated buyer can exploit this by marking orders as paid, allowing for obtaining goods without payment or settling other members' orders. The vulnerability can be exploited by generating a payment log via /member/payment/load and requesting /member/payment/test_post_pay_{paymentLogSn}. The affected product deployments should be identified, and defenders should prioritize verifying the presence of this vulnerability in their inventory.
Defensive priority
Defenders should prioritize verifying the presence of this vulnerability in their inventory, especially if using BizSpring Shop or BizSpring Java Mall. They should also monitor for unauthorized use of the test_post_pay endpoint and verify payment logs for suspicious activity.
Recommended defensive actions
- Verify the presence of this vulnerability in your inventory, especially if using BizSpring Shop or BizSpring Java Mall
- Monitor for unauthorized use of the test_post_pay endpoint
- Verify payment logs for suspicious activity
- Restrict access to the PaymentController.testPostPay handler
- Implement compensating controls for exposed systems while remediation is scheduled and verified
- Review asset inventory for affected product deployments
- Track exceptions and retest remediated assets
Evidence notes
The CVE record and source item provide details about the vulnerability, including its description and affected versions. However, the corpus does not provide information on exploitation or specific victims.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-110607 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-110607
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-110607 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-110607
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
BizSpring Shop through commit cf22d39daaf1 Payment Bypass via test_post_pay Endpoint
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/110xxx/CVE-2026-110607.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://hackmd.io/@1ExmmukzRMWN7B4gQ4W-4Q/bizspring-shop-test-pay-endpoint-order-settlement-bypass
Supplemental source - third-party-advisory
-
Source reference
Unverified legacy reference
URL: https://hackmd.io/@1ExmmukzRMWN7B4gQ4W-4Q/bizspring-java-mall-payment-forgery-order-idor
Supplemental source - third-party-advisory
-
Source reference
Unverified legacy reference
URL: https://github.com/BizSpringSource/bizspring-shop-opensource/blob/cf22d39daaf17f430d8fc1fb698a2f6e515e1808/bizspring-open/bizspring-business/bizspring-order/src/main/java/cn/bizspring/cloud/order/admin/controller/shop/PaymentController.java
Supplemental source - technical-description
-
Source reference
Unverified legacy reference
URL: https://github.com/BizSpringSource/bizspring-shop-opensource/blob/cf22d39daaf17f430d8fc1fb698a2f6e515e1808/bizspring-open/bizspring-business/bizspring-order/src/main/java/cn/bizspring/cloud/order/admin/service/impl/PaymentLogServiceImpl.java
Supplemental source - technical-description
-
Source reference
Unverified legacy reference
URL: https://github.com/bizspring-open/BizSpring-Java-Mall/blob/369e88c5cda36ddcea56742c335ee1bfe50e8156/bizspring-java/bizspring-business/bizspring-order/src/main/java/cn/bizspring/cloud/order/admin/controller/shop/PaymentController.java
Supplemental source - technical-description
-
Source reference
Unverified legacy reference
URL: https://github.com/BizSpringSource/bizspring-shop-opensource
Supplemental source - product
-
Source reference
Unverified legacy reference
URL: https://github.com/bizspring-open/BizSpring-Java-Mall
Supplemental source - product
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.