CVE-2022-23131 | Unsafe client-side session storage leading to authentication bypass/instance takeover via Zabbix Frontend with configured SAML

Exp

In the case of instances where the SAML SSO authentication is enabled (non-default), session data can be modified by a malicious actor, because a user login stored in the session was not verified. Malicious unauthenticated actor may exploit this issue to escalate privileges and gain admin access to Zabbix Frontend. To perform the attack, SAML authentication is required to be enabled and the actor has to know the username of Zabbix user (or use the guest account, which is disabled by default).

Published: 2022-01-13 Last update: 2025-10-30 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-23131 is rated Critical Active Threat (96.1/100): CVSS Critical severity, with high exploitation likelihood (EPSS 94.05%, 100th percentile). CISA KEV confirms active exploitation (added 2022-02-22) affecting Zabbix / Frontend. a weakness (CWE-290) Unauthenticated remote administrative access may be possible. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2022-23131

Name: Zabbix Frontend Authentication Bypass Vulnerability · CISA KEV detail

Exploit added: 2022-02-22

Action due: 2022-03-08

Required action: Apply updates per vendor instructions.

Exploit prediction scoring system (EPSS) score for CVE-2022-23131

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-13 94.30% 94.05% -0.26%
2 2025-11-21 93.97% 94.30% +0.34%
3 2025-11-18 — 93.97% —

Full EPSS history (28 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-23131

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.1 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 5.2 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
5.1 2.0 MEDIUM
AV:N/AC:H/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:H)
Exploitation requires uncommon or highly specific conditions.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 4.9 6.4 [email protected]

Weakness enumeration for CVE-2022-23131

OS Trackers for CVE-2022-23131

vendor priority summary link
debian unimportant CVE-2022-23131 unimportant priority: Debian including 1 source packages (zabbix), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-23131
suse critical CVE-2022-23131 severity critical: SUSE including 2 source package names (zabbix, zabbix-agent), 28 product×package rows across 15 product lines (HPE Helion OpenStack 8, SUSE Linux Enterprise High Performance Computing 12 SP5, … (15 product lines)): Known Not Affected 28. https://www.suse.com/security/cve/CVE-2022-23131/
ubuntu medium CVE-2022-23131 medium priority: Ubuntu including 1 source packages (zabbix), 12 status rows across 12 suites (bionic, focal, hirsute, impish, jammy, kinetic, lunar, mantic, noble, trusty, upstream, xenial): not-affected 6, ignored 4, DNE 1, released 1. https://ubuntu.com/security/CVE-2022-23131

Affected software / configurations for CVE-2022-23131

Vendor Product Version Raw CPE
zabbix zabbix >= 5.4.0, <= 5.4.8 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*
zabbix zabbix 6.0.0 cpe:2.3:a:zabbix:zabbix:6.0.0:alpha1:*:*:*:*:*:*

References for CVE-2022-23131

cvelogic Threat Intelligence