# CVE-2026-110607: BizSpring Shop through commit cf22d39daaf1 Payment Bypass via test_post_pay Endpoint

> Authenticated users can bypass payment verification to obtain goods without paying or settle other members' orders.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-r6p5-w7hv-x5rq

## What is CVE-2026-110607?

CVE-2026-110607 is a high-severity vulnerability in BizSpring Java Mall, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

BizSpring Shop through commit cf22d39daaf1 contains a payment verification bypass vulnerability that allows authenticated buyers to mark orders paid by calling the PaymentController.testPostPay handler. Attackers can generate a payment log via /member/payment/load and request /member/payment/test_post_pay_{paymentLogSn} to obtain goods without paying or settle other members' orders.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-110607?


## How do I fix CVE-2026-110607?

No fix has been published for CVE-2026-110607 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110607 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110607 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110607 and fix it if it is affected.

What it is: CVE-2026-110607 is a high-severity vulnerability in BizSpring Java Mall, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110607 exists.

Affected product: BizSpring Java Mall. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110607/ (Markdown: https://insights.sbomify.com/CVE-2026-110607/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110607
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110607
- OSV: https://osv.dev/vulnerability/CVE-2026-110607

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110607/
Summaries are generated and may contain mistakes; the official description above is the record.