Easy Digital DownloadsWordPress extension · Awesomemotive
CVE-2019-15116
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 easy-digital-downloads plugin before 2.9.16 for WordPress has XSS related to IP address logging.
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 confidenceCross-site scripting (XSS) vulnerability in Easy Digital Downloads WordPress plugin before version 2.9.16 allows injection of malicious scripts through IP address logging functionality. User-supplied IP addresses are not properly sanitized before being stored and displayed in the admin dashboard, potentially allowing authenticated attackers to execute arbitrary JavaScript in the context of other users' browsers.
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
Easy Digital DownloadsWordPress extension
< 2.9.16CVSS 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.1/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.
-
Verify Easy Digital Downloads is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Easy Digital Downloads' in the list. Note whether it is active or not.Affected if The plugin is installed and active
-
Check the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and click on 'View details' for Easy Digital Downloads, or check the plugin header in the main plugin file (edd.php) to find the version number.Affected if The version number is less than 2.9.16
-
Confirm IP logging functionality is in useIn the WordPress admin, navigate to Downloads > Settings > Misc (or similar logging settings area). Look for options related to 'Log IP addresses' or 'Payment Logging' - check if this feature is enabled.Affected if IP address logging is enabled in the plugin settings
-
Examine stored IP addresses in the databaseAccess the WordPress database (via phpMyAdmin or command line) and query the posts table or any edd_logs table for payment/download logs. Inspect the IP address fields for any entries containing script tags or unusual characters.Affected if IP address log entries contain unsanitized HTML/JavaScript content
You are affected if Easy Digital Downloads plugin versions below 2.9.16 are installed with IP address logging enabled and unsanitized IP addresses exist in the logs.
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.9.16
Update Easy Digital Downloads plugin to version 2.9.16 or later to receive the security patch that properly sanitizes IP address input in the logging functionality.
Fix this in Easy Digital Downloads
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-2019-15116 — 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-2019-15116 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