Threats / Zabbix / CVE-2022-23131
CVE-2022-23131
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Zabbix Frontend vulnerability
Unsafe client-side session storage in Zabbix Frontend with SAML authentication allows attackers to bypass authentication and take over instances.
Verdict
Today item — known-exploited.
An authentication bypass vulnerability in Zabbix Frontend stems from improper session storage on the client side when SAML is configured. Attackers can manipulate stored session data to gain unauthorized access and assume control of monitoring infrastructure.
CISA KEV Yes · 2022-02-225EPSS 0.95683 (verify live)6Exploit Weaponized · public PoC7CVSS 9.13CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-02-22).
Probability (EPSS)
EPSS 0.95683 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) · Affected: Zabbix, Frontend. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-290 Auth Bypass by Spoofing — weakness family: Authentication.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 40 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify that session tokens are stored insecurely on the client side in the Zabbix Frontend.
Business
Attackers gain unauthorized administrative access to the monitoring platform without valid credentials.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I modify or forge the client-side session data to impersonate legitimate users.
Business
Threat actors assume the identity and privileges of authenticated administrators or operators.
3
Lateral reach — past segmentation narrative 3
Attacker
I use the forged session to access the Zabbix instance and modify monitoring configurations.
Business
Attackers disable alerts, alter thresholds, or blind the organization to active security incidents.
4
Data at risk — exfiltration narrative 4
Attacker
I escalate access to modify infrastructure policies or extract sensitive monitoring data.
Business
Complete compromise of the monitoring infrastructure enables lateral movement and data exfiltration.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05