Quick answers
- Is CVE-2024-25170 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-25170 being exploited in the wild.
- How severe is CVE-2024-25170?
- Informational severity, with a CVSS score of 0, published 7 July 2026.
- Which products and versions are affected?
- Mezzanine CMS 0.0 through 6.0.0; Mezzanine (PyPI) ECOSYSTEM:introduced=0,last_affected=6.0.0.
- Is there a fix for CVE-2024-25170?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2024-25170 attacked?
- It is attacked over the network.
- Am I affected by CVE-2024-25170?
- Check whether you run Mezzanine CMS or Mezzanine (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an incorrect access control issue in Mezzanine v6.0.0 and earlier versions where Host header validation is insufficient or missing in access control checks. An attacker can send specially crafted HTTP requests with a manipulated Host header to bypass authentication or authorization mechanisms. The vulnerability is remotely exploitable without authentication and requires only network access to a Mezzanine instance. By exploiting this flaw, an attacker can gain unauthorized access to protected resources or functionality that should be restricted. While a proof-of-concept has been documented, official patch status is not clearly indicated in available sources.
Affected products
- Mezzanine Mezzanine CMS 0.0 through 6.0.0
Identifiers
- CVE-2024-25170
- GHSA-22cc-w7xm-rfhx
- PYSEC-2026-1626
Timeline
- 2024-02-28: disclosed
- 2024-01-10: other: Vulnerability discovered and reported