CVE-2017-8874
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 · uneditedMultiple cross-site request forgery (CSRF) vulnerabilities in Mautic 1.4.1 allow remote attackers to hijack the authentication of users for requests that (1) delete email campaigns or (2) delete contacts.
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 1.4.1 contains multiple CSRF vulnerabilities in its campaign and contact deletion functions. Attackers can craft malicious pages that, when visited by authenticated administrators, trigger the browser to send delete requests for email campaigns or contacts without the user's knowledge or consent, leveraging the lack of anti-CSRF token validation on these state-changing endpoints.
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.4.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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Verify Mautic installation versionAccess the Mautic admin dashboard and navigate to the version information page, typically found in the footer of admin pages or in the System Information section under Configuration. Alternatively, check the version file in the installation directory if you have file system access.Affected if The installed version is exactly 1.4.1 of Acquia Mautic
-
Inspect campaign deletion endpoint for CSRF protectionAs an authenticated administrator, use browser developer tools to examine the HTML source of the campaign list page or campaign deletion form. Look for a hidden input field containing a CSRF token (commonly named 'mautic_token', '_token', or similar) within the form that submits to the campaign delete action.Affected if The campaign deletion form or AJAX request lacks a CSRF token parameter, meaning the delete operation can be triggered without a valid anti-CSRF token
-
Inspect contact deletion endpoint for CSRF protectionAs an authenticated administrator, examine the HTML source of the contact list page or contact deletion form using browser developer tools. Search for a hidden CSRF token field in the form that performs contact or bulk contact deletion.Affected if The contact deletion form or AJAX request lacks a CSRF token parameter, meaning the delete operation can be triggered without a valid anti-CSRF token
-
Test deletion endpoint behavior with missing tokenIf you have testing capability, attempt to send a campaign or contact deletion request (via curl or similar) to the respective endpoint without including any CSRF token parameter and observe whether the deletion still executes.Affected if The deletion request succeeds without requiring a valid CSRF token, confirming the vulnerability is present
You are affected if your Mautic installation is version 1.4.1 AND the campaign and contact deletion endpoints do not validate CSRF tokens.
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 anti-CSRF tokens (synchronizer token pattern or SameSite cookies) on all deletion forms and AJAX endpoints in Mautic, particularly campaign and contact management functions, and ensure proper server-side token validation before executing state-changing operations.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8874 — 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-2017-8874 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