# CVE-2026-120201: Jpom 2.10.0 through 2.11.12 Authentication Bypass via JPOM-USER-TOKEN Header


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Oct 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-mr28-xw2h-9rw4

## What is CVE-2026-120201?

CVE-2026-120201 is a critical vulnerability in dromara Jpom, published on 31 Oct 2026. 

### Official description

Jpom 2.10.0 through 2.11.12 contains an authentication bypass vulnerability that allows unauthenticated attackers to gain super-administrator access by injecting query conditions into the JPOM-USER-TOKEN header. Attackers can send a value like 'is not null', which Hutool's Condition parser treats as an operator, then execute commands through Jpom's script features.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

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

It affects 1 product.


Products: Jpom.

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

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

## Is CVE-2026-120201 being exploited?

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

Public exploit code:

- Jpom 2.10.0-2.11.12 - Authentication Bypass (nuclei): http/cves/2026/CVE-2026-120201.yaml

## Other vulnerabilities in dromara Jpom

- [CVE-2026-111605](https://insights.sbomify.com/CVE-2026-111605/): Jpom through 2.11.12 Cross-Workspace Authorization Bypass via SshFileController (high 8.6)
- [CVE-2026-91993](https://insights.sbomify.com/CVE-2026-91993/): Jpom through 2.11.12 Workspace Isolation Bypass via /build/branch-list (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120201 is a critical vulnerability in dromara Jpom, published on 31 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120201 exists.

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

## Sources

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

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