CVE-2025-29573 json
Mezzanine CMS Cross-Site Scripting (XSS) vulnerability
published 2025-05-05 18 mo ago modified 2026-06-17 4 mo ago also GHSA-2544-hpcq-6g27 , PYSEC-2025-136 , EUVD-2025-13438
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
Cross-Site Scripting (XSS) vulnerability exists in Mezzanine CMS 6.0.0 in the "View Entries" feature within the Forms module.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- squadappsec.com https://www.squadappsec.com/post/cve-2025-29573-persistent-xss-in-mezzanine-cms-6-0-0-via-malicious-filename referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| OSV | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | mezzanine | <=6.0.0 |
no fix listed |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
squadappsec.com
/post/cve-2025-29573-persistent-xss-in-mezzanine-cms-6-0-0-via-malicious-filename
web, exploit, third-party-advisory, evidence
-
github.com
/stephenmcd/mezzanine
package, product
-
nvd.nist.gov
/vuln/detail/CVE-2025-29573
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/mezzanine/PYSEC-2025-136.yaml
web
-
github.com
/advisories/GHSA-2544-hpcq-6g27
advisory
Sources
- CVE List CVE-2025-29573
- GitHub Advisory GHSA-2544-hpcq-6g27
- NVD CVE-2025-29573
- OSV PYSEC-2025-136
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.