Newsletter By SupsysticWordPress extension · Supsystic
CVE-2017-18512
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 · uneditedThe newsletter-by-supsystic plugin before 1.1.8 for WordPress has CSRF.
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 confidenceThe newsletter-by-supsystic WordPress plugin before version 1.1.8 contains a Cross-Site Request Forgery (CSRF) vulnerability. This allows attackers to trick authenticated administrators into performing unintended actions by crafting malicious requests, potentially leading to unauthorized newsletter configuration changes or subscriber management operations.
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
Newsletter By SupsysticWordPress extension
< 1.1.8CVSS 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.
-
Identify plugin versionLocate the installed version of the Supsystic Newsletter By Supsystic plugin in your WordPress installation - typically found in the plugin's main file header or readme.txtAffected if The version displayed is below 1.1.8 (for example, 1.1.7, 1.1.6, 1.0.x, etc.)
-
Verify admin access existsConfirm that administrator accounts with access to the newsletter plugin settings are present on the WordPress siteAffected if There are any administrator users on the site, as CSRF attacks target authenticated admin sessions
-
Inspect plugin source for token validationExamine the plugin PHP files that handle form submissions (especially in admin settings pages and subscriber management) for presence of CSRF token validation functions such as wp_verify_nonce or check_admin_refererAffected if The plugin code lacks CSRF token validation on forms that modify newsletter settings or subscriber data - the vulnerable version has no nonce checks
-
Check for unprotected action endpointsReview the plugin's admin action handlers to see if they validate the request origin or require authentication confirmation before executing changesAffected if The plugin processes admin actions without verifying the request authenticity, allowing forged requests from other sites
You are affected if the Supsystic Newsletter By Supsystic plugin version is below 1.1.8 AND administrator accounts exist on the site, as the vulnerability allows attackers to trick logged-in admins into making unintended configuration changes.
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 data1.1.8
Update the newsletter-by-supsystic plugin to version 1.1.8 or later, which includes CSRF token validation. If immediate update is not possible, ensure admin sessions are protected and monitor for suspicious admin actions.
Fix this in Newsletter By Supsystic
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18512 — 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-18512 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