CVE-2021-27915 is a high severity (CVSS 7.6) stored cross site scripting flaw in the description fields of Mautic, the marketing automation platform. A logged in user with the right permissions could gain elevated access. The advisory lists versions from 1.0.0-beta2 as affected and 4.4.12 as the patched version.
What's affected
- Mautic (Composer package mautic/core), versions from 1.0.0-beta2 up to the patched release, per GitHub advisory GHSA-2rc5-2755-v422.
- Patched in 4.4.12, with no workarounds listed.
- The advisory was published on 11 April 2024 and rates it High, 7.6, matching the NVD record.
- The attacker must be a logged in Mautic user with appropriate permissions, and another user has to view the injected content.
- KEV status: false.
How to check if you're exposed
Check the installed Mautic version from the admin interface, or from Composer if you installed it that way.
composer show mautic/core
Anything below 4.4.12 is affected. Also review which users can edit descriptions and who has high privilege roles that would view them.
What to do now
- Update Mautic to 4.4.12 or later. The advisory lists no workaround.
- If you run 5.x, check the advisory and release notes for your line, because the advisory names 4.4.12 as the patched version for this CVE.
- Review Mautic roles and remove edit permissions from users who do not need them.
- Check descriptions on campaigns, segments and other objects for unexpected script content.
- Add the application to your dependency scanning so Composer packages are checked on every build.
Why it matters
The record lists CWE-79, cross site scripting, and CWE-80, basic cross site scripting. Content saved in a description field was later shown to other users without enough output handling, so script could run in their browsers. In an admin console, running as a more privileged user is how a low privilege account can reach elevated access.
Stored XSS in internal tools is easy to underrate because the audience is small. But marketing platforms hold contact data and integrations. A script running in an admin session can act as that admin.
The fix is a version bump, but the lasting lesson is about output encoding and about how many people hold privileged roles. Review which roles can write free text fields that other users will read, and treat those roles as sensitive. If your Mautic instance connects to other systems, such as email providers or a CRM, an admin session is also a path into those.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is there a workaround?
The advisory says none. Update to 4.4.12 or later.
Does the attacker need an account?
Yes. The advisory says a logged in user with appropriate permissions.
Sources
Last reviewed: 19 October 2026.