CVE-2020-35129
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 · uneditedMautic before 3.2.4 is affected by stored XSS. An attacker with access to Social Monitoring, an application feature, could attack other users, including administrators. For example, an attacker could load an externally drafted JavaScript file that would allow them to eventually perform actions on the target user’s behalf, including changing the user’s password or email address or changing the attacker’s user role from a low-privileged user to an administrator account.
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 · high confidenceStored XSS vulnerability in Mautic's Social Monitoring feature (versions before 3.2.4) allows authenticated low-privilege users to inject malicious JavaScript that executes in the browsers of other users, including administrators. The attacker can load external JavaScript files to perform actions on behalf of victims, enabling account takeover and privilege escalation from regular user to administrator.
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< 3.2.4CVSS 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 versionAccess the Mautic administration panel and navigate to System Information or check the version file in the Mautic installation directory (app/config/version.php or similar). Alternatively, check the footer of any Mautic admin page for the version number.Affected if The installed version is below 3.2.4 (for example, 3.2.3, 3.2.0, or earlier releases).
-
Verify Social Monitoring feature statusIn the Mautic admin panel, navigate to the Social Monitoring section (typically found under Channels or Marketing menu). Check whether any social monitoring entries exist or have been configured.Affected if Social Monitoring is accessible or configured in the Mautic instance, regardless of whether the current user has created entries.
-
Confirm user role permissions for Social MonitoringGo to Roles and Permissions in Mautic admin panel. Examine the permissions assigned to user roles, specifically checking for permissions related to Social Monitoring (monitoring, social, or similar permission categories).Affected if Low-privilege users (non-admin roles) have permissions to access or create Social Monitoring entries.
-
Review recent Social Monitoring activity logsAccess the audit log or activity log within Mautic. Filter or search for events related to Social Monitoring, looking for recent entries created by any user.Affected if Any Social Monitoring entries were created recently by users with low-level privileges, or entries contain unexpected or encoded content.
A Mautic installation is affected if it runs version 3.2.4 or lower AND the Social Monitoring feature is accessible to authenticated users, particularly low-privilege accounts.
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 · scoped3.2.4
Upgrade Mautic to version 3.2.4 or later which contains the patch for this stored XSS vulnerability.
Mautic 3.2.4
- Backup your Mautic database and files before starting the upgrade process
- Enable maintenance mode to prevent user access during upgrade
- Upgrade Mautic to version 3.2.4 or later (e.g., using the command line: php bin/console mautic:update:find and php bin/console mautic:update:apply, or via your package manager)
- Clear the Mautic cache after upgrade (php bin/console cache:clear)
- Verify the upgrade was successful by logging in and checking the Social Monitoring feature
- Disable maintenance mode once verification is complete
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35129 — 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-2020-35129 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