# CVE-2026-2010: Sanluan PublicCMS Trade Payment TradePaymentService.java paid improper authorization

> Attackers can bypass authorization in the trade payment service to manipulate payment states, requiring a patch for PublicCMS.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 6 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-52jq-ww84-hqvp

## What is CVE-2026-2010?

CVE-2026-2010 is a low-severity missing authorization vulnerability in Sanluan PublicCMS, published on 6 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in Sanluan PublicCMS up to 4.0.202506.d/5.202506.d/6.202506.d. Impacted is the function Paid of the file publiccms-parent/publiccms-trade/src/main/java/com/publiccms/logic/service/trade/TradePaymentService.java of the component Trade Payment Handler. The manipulation of the argument paymentId leads to improper authorization. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitability is considered difficult. The exploit has been disclosed to the public and may be used. The identifier of the patch is 7329437e1288540336b1c66c114ed3363adcba02. It is recommended to apply a patch to fix this issue.

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

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

It affects 1 product.


Products: Publiccms Publiccms.

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

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

## Is CVE-2026-2010 being exploited?

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

## Other vulnerabilities in Sanluan PublicCMS

- [CVE-2025-25361](https://insights.sbomify.com/CVE-2025-25361/): File upload in n/a (critical 9.8)
- [CVE-2023-46990](https://insights.sbomify.com/CVE-2023-46990/): Deserialization in n/a (critical 9.8)
- [CVE-2023-34852](https://insights.sbomify.com/CVE-2023-34852/): Missing authorization in n/a (critical 9.8)
- [CVE-2020-20914](https://insights.sbomify.com/CVE-2020-20914/): SQL injection in n/a (critical 9.8)
- [CVE-2020-20915](https://insights.sbomify.com/CVE-2020-20915/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2010 is a low-severity missing authorization vulnerability in Sanluan PublicCMS, published on 6 Feb 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-2010 exists.

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-2010/ (Markdown: https://insights.sbomify.com/CVE-2026-2010/index.md)
```

## Sources

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

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