# CVE-2024-25169: Mezzanine allows attackers to bypass access control mechanisms

> Attackers can bypass admin panel access controls in Mezzanine via crafted requests, requiring an upgrade to secure the application.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Feb 2024
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-qp56-82vp-xqgv, PYSEC-2026-1627

## What is CVE-2024-25169?

CVE-2024-25169 is a critical authentication bypass vulnerability in n/a, published on 28 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Mezzanine v6.0.0 allows attackers to bypass access control mechanisms in the admin panel via a crafted request.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-25169?

3 open source packages ship an affected version, including mezzanine and Mezzanine. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mezzanine` | PyPI | All versions to 6.0.0 | None |
| `mezzanine` | PyPI | All versions to 6.0.0 | None |
| `Mezzanine` | PyPI | All versions to 6.0.0 | None |

Products: Jupo Mezzanine.

## How do I fix CVE-2024-25169?

No fix has been published for CVE-2024-25169 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-25169 being exploited?

There is no known exploitation of CVE-2024-25169 in the wild and no public exploit code.

Public exploit code:

- https://github.com/shenhav12/CVE-2024-25169-Mezzanine-v6.0.0 (github_poc): https://github.com/shenhav12/CVE-2024-25169-Mezzanine-v6.0.0

## Other vulnerabilities in n/a

- [CVE-2024-25170](https://insights.sbomify.com/CVE-2024-25170/): Mezzanine allows attackers to bypass access controls via manipulating the Host header (critical 9.1)
- [CVE-2025-29573](https://insights.sbomify.com/CVE-2025-29573/): Mezzanine CMS Cross-Site Scripting (XSS) vulnerability (medium 6.1)
- [CVE-2020-19002](https://insights.sbomify.com/CVE-2020-19002/): Mezzanine Cross Site Scripting (XSS) vulnerability (medium 6.1)
- [CVE-2025-50481](https://insights.sbomify.com/CVE-2025-50481/): Mezzanine CMS vulnerable to Cross-site Scripting (medium 4.8)
- [CVE-2025-6050](https://insights.sbomify.com/CVE-2025-6050/): Stored Cross-Site Scripting (XSS) in Mezzanine CMS Admin Interface (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25169 and fix it if it is affected.

What it is: CVE-2024-25169 is a critical authentication bypass vulnerability in n/a, published on 28 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-25169 in the wild and no public exploit code.

Affected packages and fixed versions:
- mezzanine (PyPI): affected all versions up to 6.0.0; no fix listed
- mezzanine (PyPI): affected all versions up to 6.0.0; no fix listed
- Mezzanine (PyPI): affected all versions up to 6.0.0; no fix listed

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-2024-25169/ (Markdown: https://insights.sbomify.com/CVE-2024-25169/index.md)
```

## Sources

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

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