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

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of 10 Nov 2026. If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?

2.1%

Up from 0.6% on 5 Nov 2026.

EPSS score, percentile 82.3 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?

9.3 Critical

CVSS v4.0 base score, given by the CNA

What should I do?

CISA has set no required action, because the vulnerability is not in KEV.

No patch or vendor advisory is listed in the CVE record. Check dromara's advisories.

Which versions are affected?

Affected

• 2.10.0 through 2.11.12

Versions by product

Source: CISA KEV 2026.11.10, as of 10 Nov 2026; FIRST EPSS, as of 12 Nov 2026; CVE List, as of 12 Nov 2026. About the data.

Description

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

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.

Source: CVE List, as of 12 Nov 2026. About the data.

What to do

Advisories and patches

No patch, vendor advisory or mitigation is listed in the CVE record. Check dromara's own security advisories for a fix, and compare your version with the affected versions below.

This summary is based on the CVE record as of 12 Nov 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

Source: CVE List, as of 12 Nov 2026. About the data.

Timeline