CVE-2018-11198
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 · uneditedAn issue was discovered in Mautic 2.13.1. There is Stored XSS via the authorUrl field in config.json.
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 2.13.1 where the authorUrl field in config.json does not properly sanitize user input, allowing injection of malicious JavaScript that executes when the configuration is viewed or processed.
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.1CVSS 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 versionAccess the Mautic admin dashboard and navigate to Settings > Configuration, or check the version file in your Mautic installation (typically in app/constants.php or similar version file)Affected if The installed version is exactly 2.13.1
-
Locate config.jsonFind the config.json file in your Mautic installation directory, typically found in the root or config folder of the Mautic applicationAffected if You locate a config.json file in your Mautic installation
-
Inspect authorUrl fieldOpen the config.json file and locate the authorUrl field within the configurationAffected if The authorUrl field exists and contains any HTML tags (such as <script>, <img>, or javascript:), or contains unusual characters that could indicate injected code
-
Verify configuration display accessAttempt to access the Mautic configuration page where authorUrl would be displayed (typically Settings > Configuration > General Settings or similar)Affected if You can access the configuration page and view the authorUrl value in the interface
-
Check for unexpected script executionView the page source of the configuration page and search for the authorUrl value to see if it is being rendered with raw HTML/JS rather than being escapedAffected if The authorUrl value is rendered as raw HTML without encoding, allowing script execution
You are affected if you are running Mautic version 2.13.1 AND your config.json contains an authorUrl field with unescaped HTML or JavaScript code that would execute when the configuration page 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 dataImplement proper input validation and output encoding for the authorUrl field, or upgrade to a patched version if available. Sanitize the URL to ensure it contains only safe, valid URL characters.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11198 — 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-11198 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