CVE & CISA-KEV Catalog

CVE-2022-23131

CRITICALCISA KEVEPSS 100th pctl
9.1
CVSS v3
NVD

Description

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

How to fix

Actively exploited, no published fix found yet

CISA required action: Apply updates per vendor instructions.

Federal remediation due: 2022-03-08

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityHigh
AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploit Intelligence

95.68%probability of exploitation in 30 days
100thpercentile

Very high risk: more likely to be exploited than 100% of all known CVEs.

Known Exploited Vulnerability (CISA KEV)

Zabbix Frontend Authentication Bypass Vulnerability

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

Apply updates per vendor instructions.

Remediation due: 2022-03-08

References

Government Resource1

Related Vulnerabilities

Other CWE-290 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2024-4358Critical9.897%KEV-
CVE-2022-24112Critical9.896%KEVFix
CVE-2019-1234High7.574%--
CVE-2021-31195Medium6.574%-Fix
CVE-2021-29441High8.670%-Fix
CVE-2020-7388Critical10.069%-Fix

Common questions

How do I fix CVE-2022-23131?

No published fix for CVE-2022-23131 has been found yet. It is on the CISA Known Exploited Vulnerabilities list; federal agencies must remediate by 2022-03-08. Apply the vendor's mitigations per CISA's guidance.

Is CVE-2022-23131 being actively exploited?

Yes. CVE-2022-23131 is listed in the CISA Known Exploited Vulnerabilities catalog, which means exploitation has been observed in the wild. US federal agencies were required to remediate it by 2022-03-08. Treat it as a priority whatever its CVSS score says.

How severe is CVE-2022-23131?

CVE-2022-23131 has a CVSS v3 base score of 9.1, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2022-23131
CVE-2022-23131 severity badge

Markdown

[![CVE-2022-23131](https://tridentstack.com/cve/badge/CVE-2022-23131.svg)](https://tridentstack.com/cve/CVE-2022-23131)

HTML

<a href="https://tridentstack.com/cve/CVE-2022-23131"><img src="https://tridentstack.com/cve/badge/CVE-2022-23131.svg" alt="CVE-2022-23131"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2025-10-30.