CASCACascade Atlas

Evidence dossier

CVE-2022-23131

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

72.3–99.1Priority evidence range
As known Jul 19, 2026, 5:00 AM UTCgen-56ccdaf9

Normalized restatement

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).

State
PUBLISHED
Published
Jan 13, 2022
Updated
Oct 21, 2025
Evidence coverage
72%
CISA KEVCatalog member

Apply updates per vendor instructions.

FIRST EPSS95.68%

2026-07-18 · v2026.06.15 · percentile 99.9%

Source stateConflict visible

Distinct CVSS assessments remain side by side; none are averaged.

Source comparison

Who said what

CISA-ADPindependent enrichment
container

CISA ADP Vulnrichment

CVEderivative copy
container

CVE Program Container

Zabbixoriginal assertion
container

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

CISA KEVoriginal assertion
observed_exploitation

Zabbix Frontend Authentication Bypass Vulnerability

FIRST EPSSoriginal assertion
model_probability

Probability 0.956830000000; percentile 0.998630000000

Applicability

Cited product scope

Trace impact →
ZabbixFrontend
[{"status": "affected", "version": "5.4.0 - 5.4.8"}, {"status": "unaffected", "version": "5.4.9", "lessThan": "5.4.9*", "versionType": "custom"}]unknown
Unknown vendorUnknown product
cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*; start including 5.4.0; end including 5.4.8supported
Unknown vendorUnknown product
cpe:2.3:a:zabbix:zabbix:6.0.0:alpha1:*:*:*:*:*:*supported

Assessments

CVSS by origin

9.8
nvd@nist.govCVSS 3.1 · role PrimaryCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
5.1
nvd@nist.govCVSS 2.0 · role PrimaryAV:N/AC:H/Au:N/C:P/I:P/A:P
9.1
security@zabbix.comCVSS 3.1 · role SecondaryCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
9.1
ZabbixCVSS 3.1 · role unknownCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Limitations and unknowns

  • KEV membership is authoritative for the catalog, not proof of exposure in any environment.
  • EPSS is a dated model probability and not an individual-environment prediction.
  • Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
  • NVD-carried upstream facts remain derivative and are not independent corroboration.
  • Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
  • NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
  • Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
  • Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.