basicsecurity.net
Proof, not just disclosure.
Threats / Zabbix / CVE-2022-23131
CVE-2022-23131 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-223EPSS 0.95683 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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).
CISA KEV ↗Confirmed
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
Affected: Zabbix, Frontend. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-290 Auth Bypass by Spoofing — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 2 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by Zabbix (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by ZabbixCNA
    Credited with finding itZabbix wants to thank Thomas Chauchefoin from SonarSource for reporting this issue to usunspecified