# CVE-2026-124565: fushengqian fuint Order Verification MerchantOrderController.java confirm access control


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-v47m-7h34-6c9w

## What is CVE-2026-124565?

CVE-2026-124565 is a medium-severity vulnerability in fushengqian fuint, published on 9 Nov 2026. 

### Official description

A security vulnerability has been detected in fushengqian fuint up to 36cc31b08d77facc94e8959afa02224891b4fe5f. This affects the function confirm of the file MerchantOrderController.java of the component Order Verification. Such manipulation leads to improper access controls. The attack can be executed remotely. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-124565 being exploited?

There is no known exploitation of CVE-2026-124565 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124565 is a medium-severity vulnerability in fushengqian fuint, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124565 in the wild and no public exploit code.

Affected product: fushengqian fuint. 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-124565/ (Markdown: https://insights.sbomify.com/CVE-2026-124565/index.md)
```

## Sources

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

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