CVE-2021-27915
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPrior to the patched version, there is an XSS vulnerability in the description fields within the Mautic application which could be exploited by a logged in user of Mautic with the appropriate permissions. This could lead to the user having elevated access to the system.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStored XSS vulnerability in Mautic's description fields that can be exploited by authenticated users with appropriate permissions. The flaw allows injection of malicious scripts into description inputs, which could enable privilege escalation by compromising admin sessions or performing actions on behalf of higher-privileged users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.0.0, < 4.4.12= 1.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mautic versionLocate the Mautic version in the admin dashboard under Configuration > System Info or check the version file in the Mautic installation directoryAffected if Version is 1.0.0 or any version >= 1.0.0 and < 4.4.12
-
Review user roles with description field accessIn Mautic admin panel, navigate to Users > Roles and Permissions to identify which authenticated user roles have create or edit permissions for elements containing description fields (such as categories, segments, or custom objects)Affected if Any authenticated user role has permissions to access and modify description fields
-
Test description field for input sanitizationUsing a user account with description field permissions, attempt to insert a test script tag such as <script>alert('XSS')</script> into a description field and save the recordAffected if The script tag is stored and rendered without being escaped or sanitized when the record is displayed
You are affected if your Mautic version is 1.0.0 or between 1.0.0 and 4.4.11 inclusive AND authenticated users with description field edit permissions exist in your system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.4.12
Apply the patched version of Mautic that includes proper input sanitization and output encoding for description fields. Review and validate all user-supplied input in similar fields throughout the application.
Mautic 4.4.12 or later
- Verify current Mautic version by checking the application or config file
- Backup the Mautic database and files before upgrading
- Download Mautic version 4.4.12 or the latest stable release from the official Mautic repository (github.com/mautic/mautic)
- Follow Mautic upgrade documentation to apply the update
- Clear application cache after upgrade
- Verify the upgrade was successful and test that the description fields function correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-27915 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data