# CVE-2022-23131: Zabbix Frontend Authentication Bypass

> Attackers can bypass authentication and gain admin access in Zabbix Frontend if SAML SSO is enabled, due to unverified session data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Yes, since 22 Feb 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-4g73-3mxf-j47w

## What is CVE-2022-23131?

CVE-2022-23131 is a critical authentication bypass vulnerability in Zabbix Zabbix, published on 13 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2022-23131?

It affects 1 product.


Products: Zabbix Zabbix.

## How do I fix CVE-2022-23131?

No fix has been published for CVE-2022-23131 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 8 Mar 2022.

## Is CVE-2022-23131 being exploited?

Yes. Attackers have exploited CVE-2022-23131 in the wild since at least 22 Feb 2022.

Public exploit code:

- cve-2022-23131 zabbix-saml-bypass-exp (github_poc): https://github.com/Mr-xn/cve-2022-23131
- cve-2022-23131 exp (github_poc): https://github.com/jweny/CVE-2022-23131
- cve-2022-23131 (github_poc): https://github.com/L0ading-x/cve-2022-23131
- Zabbix - SAML SSO Authentication Bypass (github_poc): https://github.com/kh4sh3i/CVE-2022-23131
- CVE-2022-23131漏洞利用工具开箱即用。 (github_poc): https://github.com/Kazaf6s/CVE-2022-23131
- Zabbix SSO Bypass (github_poc): https://github.com/random-robbie/cve-2022-23131-exp

## Other vulnerabilities in Zabbix Zabbix

- [CVE-2007-0640](https://insights.sbomify.com/CVE-2007-0640/): Memory corruption in n/a (critical 10.0)
- [CVE-2024-42327](https://insights.sbomify.com/CVE-2024-42327/): SQL injection in user.get API (critical 9.9)
- [CVE-2024-22116](https://insights.sbomify.com/CVE-2024-22116/): Remote code execution within ping script (critical 9.9)
- [CVE-2013-3738](https://insights.sbomify.com/CVE-2013-3738/): Code injection in n/a (critical 9.8)
- [CVE-2013-5743](https://insights.sbomify.com/CVE-2013-5743/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23131 and fix it if it is affected.

What it is: CVE-2022-23131 is a critical authentication bypass vulnerability in Zabbix Zabbix, published on 13 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-23131 in the wild since at least 22 Feb 2022.

Affected product: Zabbix Zabbix. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-23131/ (Markdown: https://insights.sbomify.com/CVE-2022-23131/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-23131
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-23131
- OSV: https://osv.dev/vulnerability/CVE-2022-23131

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-23131/
Summaries are generated and may contain mistakes; the official description above is the record.