CVE-2018-8071
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 v2.13.0 has stored XSS via a theme config file.
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 confidenceMautic before v2.13.0 contains a stored cross-site scripting (XSS) vulnerability in theme configuration files. An attacker can inject malicious JavaScript code into theme config files which will be executed when administrators or users view the affected theme.
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< 2.13.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Check Mautic versionLocate the version file or configuration file in your Mautic installation (typically app/config/config.php or a VERSION file in the root directory) and identify the installed version number.Affected if The installed version is lower than 2.13.0
-
Locate theme configuration filesNavigate to the themes directory in your Mautic installation (typically app/themes/ or themes/) and identify all subdirectories containing config files.Affected if Custom or third-party themes are present in the themes directory
-
Inspect theme config files for malicious script contentOpen each theme's configuration file (commonly named config.json, config.php, or theme.json) and search for suspicious patterns such as <script> tags, javascript: URIs, event handlers (onclick, onload, onerror), or encoded JavaScript payloads.Affected if Any theme configuration file contains executable JavaScript code or event handler attributes
-
Verify if themes are actively loadedCheck the Mautic dashboard or theme settings to see which themes are currently enabled or assigned to landing pages or emails.Affected if An affected theme with malicious configuration is actively enabled or used in the application
You are affected if your Mautic installation version is below 2.13.0 AND any theme configuration file contains injectable JavaScript code that could execute when the theme is viewed.
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.
From vendor data2.13.0
Upgrade Mautic to version 2.13.0 or later to receive the patch for this vulnerability. If immediate upgrade is not possible, audit existing custom theme configurations for malicious content and disable untrusted themes.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8071 — 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-2018-8071 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