Jpom 2.10.0 through 2.11.12 Authentication Bypass via JPOM-USER-TOKEN Header
Jpom 2.10.0 through 2.11.12 is affected, and so was the master branch at the time of the advisory. No fixed version is listed.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Jpom, a web-based server operations and deployment management tool, is affected by this flaw. An unauthenticated attacker could bypass login and gain super-administrator control, then run commands on the server through Jpom's script features.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- dromara Jpom
From 2.10.0 · through 2.11.12
References 4
Questions about CVE-2026-120201
What does this mean?
The server passes the JPOM-USER-TOKEN header value to Hutool, which parses it as a query condition. An unauthenticated attacker can obtain a super-administrator session, then run arbitrary commands on the Jpom server and on managed hosts through node features.Source: github.com
Am I affected, and how do I check?
Jpom versions 2.10.0 through 2.11.12 are affected, and the master branch was also affected at the time of the advisory. Compare the installed Jpom version against that range to check the version in use.Source: github.com
What should I do about it?
The checked facts do not name a fixed version or upgrade target, so no specific upgrade can be recommended from them.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts do not list a workaround or interim mitigation for this issue.Source: github.com