Eelv NewsletterWordPress extension · Eelv Newsletter Project
CVE-2017-18522
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 eelv-newsletter plugin before 4.6.1 for WordPress has XSS in the address book.
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 confidenceThe eelv-newsletter WordPress plugin before version 4.6.1 contains a Cross-Site Scripting (XSS) vulnerability in its address book functionality. This allows attackers to inject malicious scripts through unsanitized input fields, which then execute in the browsers of users who view the affected address book data.
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
Eelv NewsletterWordPress extension
< 4.6.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.
-
Confirm eelv-newsletter plugin is installedNavigate to the WordPress admin panel, go to the Plugins section, and look for 'eelv-newsletter' or 'Eelv Newsletter' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Check the installed version numberIn the WordPress Plugins page, click on the eelv-newsletter plugin to view its details, or open the main plugin PHP file and locate the Version header in the plugin commentsAffected if The displayed version is less than 4.6.1
-
Determine if address book feature is activeAccess the plugin settings menu in WordPress admin and locate the address book or newsletter subscriber management section; check whether this feature is enabledAffected if Address book functionality exists and is enabled in the plugin configuration
-
Compare version against vulnerable rangeTake note of the exact installed version and confirm it is below 4.6.1 using standard version comparisonAffected if Installed version is below 4.6.1 and the address book feature is accessible to users
Environment is affected if the eelv-newsletter plugin version is below 4.6.1 and the address book feature is enabled and accessible to users.
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 data4.6.1
Update the eelv-newsletter plugin to version 4.6.1 or later to obtain the patch that sanitizes input in the address book feature. If immediate update is not possible, disable the plugin until patching is feasible.
Fix this in Eelv Newsletter
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18522 — 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-18522 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