CVE-2026-120201

Jpom 2.10.0 through 2.11.12 Authentication Bypass via JPOM-USER-TOKEN Header

Published Oct 31, 2026 CVSS 4.0 · 9.3 Critical EPSS 2.1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

This vulnerability permits an unauthenticated attacker to inject arbitrary query conditions into the JPOM-USER‑TOKEN HTTP header. The injected string is parsed by Hutool’s Condition parser as an operator, which can then be exploited to execute commands via Jpom’s script features. The result is a full super‑administrator privilege set, potentially allowing any malicious action within the application.

Affected Systems

The flaw is present in Jpom version 2.10.0 through 2.11.12. All instances of this product, regardless of deployment size or configuration, are affected.

Risk and Exploitability

With a CVSS score of 9.3 this vulnerability is considered critical. The EPSS score is 2%, indicating a low but tangible exploitation probability, and the lack of a KEV listing does not diminish the risk. The attack vector is clear: a remote attacker can send a crafted HTTP request with a special header value such as "is not null" to bypass authentication and gain administrative control, all without needing any prior credentials.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Jpom patch (e.g., 2.12.0 or later) that removes the authentication bypass flaw, effectively addressing CWE-943 by preventing invalid input from being interpreted as query conditions.
  • If a patch is not immediately possible, configure the application to reject or sanitize the JPOM-USER‑TOKEN header and disable Jpom’s script execution capabilities, mitigating CWE-943 by ensuring only valid tokens are accepted.
  • Implement network or web‑application firewall rules that block unexpected or malformed JPOM-USER‑TOKEN header values and monitor for repeated attempts, providing additional protection against CWE-943 exploitation.
  • Review and disable any legacy scripts or plugins that might allow execution of arbitrary commands, reducing the attack surface for CWE-943 exploitation.

Generated by OpenCVE AI on November 6, 2026 at 15:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:dromara:jpom:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Dromara
Dromara jpom
Vendors & Products Dromara
Dromara jpom
Type Values Removed Values Added
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.
Title Jpom 2.10.0 through 2.11.12 Authentication Bypass via JPOM-USER-TOKEN Header
Weaknesses CWE-943
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, 'vector': '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'}

Weaknesses
  • CWE-943

    Improper Neutralization of Special Elements in Data Query Logic

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 2, 2026, 2:35 PM
Reserved
Oct 31, 2026, 11:44 AM
Status
Analyzed
Published
Oct 31, 2026, 6:17 PM
Modified
Nov 9, 2026, 6:31 PM