ZenTao PMS before 22.3 contains an authorization bypass vulnerability in commonModel::isOpenMethod() that lets logged-in users skip group-based ACL checks for any method containing 'ajax'. Minimal-privilege users can call methods like task.ajaxGetByID, system.ajaxDBAuthUrl and admin.ajaxChangeTableEngine to read data, obtain database credentials, trigger CI jobs and alter tables.
CVE-2026-114391
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-10-21. A secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1HIGHhigh confidence
- EG Risk
- 32EG Risk 32/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity71% × 45%Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- Unknown (no EPSS on record)Unknown, not low: FIRST has published no EPSS probability for this CVE.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 21, 2026
Last Modified
October 21, 2026
Advisory Details (6)
Auto-updated Oct 21, 2026ZenTao PMS before 22.3 Authorization Bypass via Ajax Controller Methods | Advisories | VulnCheck
https://www.vulncheck.com/advisories/zentao-pms-before-22.3-authorization-bypass-via-ajax-controller-methods22.3
Patch available: easysoft/zentaopms zentaopms_22.3_20260707
https://github.com/easysoft/zentaopms/releases/tag/zentaopms_22.3_20260707Security: Global Authorization Bypass via Ajax Method Name Convention · Issue #181 · easysoft/zentaopms · GitHub
https://github.com/easysoft/zentaopms/issues/181commit ac484f3b01c0 (easysoft/zentaopms)
Fix landed in easysoft/zentaopms commit ac484f3b01c0 — awaiting tagged release
https://github.com/easysoft/zentaopms/commit/ac484f3b01c0f84002391a344d99dd2993692f49zentaopms/module/system/control.php at zentaopms_22.2_20260527 · easysoft/zentaopms · GitHub
https://github.com/easysoft/zentaopms/blob/zentaopms_22.2_20260527/module/system/control.php#L454-L474zentaopms/module/common/model.php at zentaopms_22.2_20260527 · easysoft/zentaopms · GitHub
https://github.com/easysoft/zentaopms/blob/zentaopms_22.2_20260527/module/common/model.php#L446-L463Vendor Advisories for CVE-2026-114391(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-21 21:26 UTCEG score recompute
- 2026-10-21 21:26 UTCGHSA enrichmentGHSA-crpg-r4ww-5jx4 · GitHub severity HIGH · GitHub CVSS 7.1
- 2026-10-21 20:26 UTCEG score recompute
- 2026-10-21 20:26 UTCGHSA enrichmentGHSA-crpg-r4ww-5jx4 · GitHub severity HIGH · GitHub CVSS 7.1
- 2026-10-21 14:29 UTCEG score recompute
- 2026-10-21 12:53 UTCMITRE cvelistV5first tracked
- 2026-10-21 12:51 UTCEG score recomputeFirst assessed: 7.1 HIGH
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-114391?
When was CVE-2026-114391 made public?
What is the CVSS score of CVE-2026-114391?
How do I remediate CVE-2026-114391?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-114391
Is Your Infrastructure Affected by CVE-2026-114391?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.