CVE-2018-10189
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 1.x and 2.x before 2.13.0. It is possible to systematically emulate tracking cookies per contact due to tracking the contact by their auto-incremented ID. Thus, a third party can manipulate the cookie value with +1 to systematically assume being tracked as each contact in Mautic. It is then possible to retrieve information about the contact through forms that have progressive profiling enabled.
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 versions 1.x and 2.x before 2.13.0 use auto-incremented contact IDs in tracking cookies, making them predictable. An attacker can manipulate the cookie value by incrementing the ID to systematically impersonate any contact in the system and retrieve information through forms with progressive profiling enabled.
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, <= 1.4.1>= 2.0.0, < 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed Mautic versionLocate the version file in your Mautic installation (typically in app/config.yml or a version.php file) and read the version numberAffected if version is >= 1.0.0 and <= 1.4.1, OR >= 2.0.0 and < 2.13.0
-
Identify forms with progressive profiling enabledIn the Mautic admin interface, navigate to the Forms section and examine each form configuration. Look for the progressive profiling setting in form settingsAffected if any form has progressive profiling enabled and the Mautic version is vulnerable
-
Inspect tracking cookie structureVisit a page on your Mautic site and examine cookies set by the domain. Look for cookies containing contact identifiers (commonly mtc_id or similar). Check if the value is a simple numeric IDAffected if the cookie value is a sequential numeric ID that can be incremented
-
Verify cookie ID predictabilityCreate multiple fresh visits (incognito/browsers without existing cookies) and compare the assigned cookie values. Increment each value by 1 and verify if the next ID is predictableAffected if cookie IDs increment sequentially without randomization
You are affected if your Mautic version is below 2.13.0 and you have any forms with progressive profiling enabled, since the tracking cookie uses predictable sequential IDs that can be manipulated to impersonate contacts.
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 to Mautic 2.13.0 or later which implements non-predictable tracking identifiers. Until patched, restrict access to forms with progressive profiling and monitor for suspicious cookie manipulation patterns.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10189 — 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-10189 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