# CVE-2026-121583: Sanluan PublicCMS TradePaymentService.java TradePaymentService.pendingRefund authorization


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-mr5q-563w-gq7x

## What is CVE-2026-121583?

CVE-2026-121583 is a medium-severity vulnerability in Sanluan PublicCMS, published on 3 Nov 2026. 

### Official description

A vulnerability was identified in Sanluan PublicCMS 5. This affects the function TradePaymentService.pendingRefund of the file publiccms-parent/publiccms-trade/src/main/java/com/publiccms/logic/service/trade/TradePaymentService.java. The manipulation of the argument userId leads to authorization bypass. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. The web trade payment controller was removed starting with the 202608 series (commit 7329437).

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-121583 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121583 is a medium-severity vulnerability in Sanluan PublicCMS, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121583 in the wild and no public exploit code.

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

## Sources

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

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