CVE-2025-50481: Mezzanine CMS Vulnerable to Cross-site Scripting (XSS)

mezzanine Updated 02 Oct 2025

Summary

23/07/2025
No i
Moderate
4.8

CVE-2025-50481: Mezzanine CMS vulnerable to Cross-site Scripting. Affects mezzanine versions < 6.1.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Mezzanine is a powerful content management system (CMS) built using the Django framework. It provides a flexible and extensible platform for managing websites, featuring a rich set of tools for content creation, user management, and site customization. However, like many web applications, it can be susceptible to security vulnerabilities, including cross-site scripting (XSS) attacks, which can compromise user data and site integrity.

Vulnerability Detail

The vulnerability identified as CVE-2025-50481 is a cross-site scripting (XSS) flaw found in the '/blog/blogpost/add' component of Mezzanine CMS version 6.1.0. This issue allows attackers to inject malicious scripts or HTML into blog posts, which can then be executed in the browsers of users who view the affected posts. The potential ramifications include unauthorized access to user sessions, data theft, and the spread of malware, making it a significant security concern for websites utilizing this CMS.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can sanitize input fields in the blog post creation form to prevent the execution of scripts. This can be done by implementing input validation and escaping user-generated content before rendering it on the page.

Conclusion

In summary, CVE-2025-50481 represents a significant security vulnerability in Mezzanine CMS that can lead to cross-site scripting attacks. It is crucial for users to update to the latest version of the software to mitigate this risk and ensure the safety of their web applications.

See every vulnerability recorded for mezzanine →

Share this vulnerability

FAQ

CVE-2025-50481 is a cross-site scripting (XSS) vulnerability in Mezzanine CMS that allows attackers to inject malicious scripts into blog posts.

The vulnerability affects Mezzanine CMS version 6.1.0 and earlier versions.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

The risks include unauthorized access to user sessions, data theft, and potential malware distribution, which can severely compromise the security of the affected website.

The CVSS score for this vulnerability is 4.8, indicating a moderate severity level.

Related vulnerabilities

Recent vulnerabilities recorded for mezzanine.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback