CVE-2015-9324
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.3.3 for WordPress has SQL injection.
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 confidenceSQL injection vulnerability in the easy-digital-downloads WordPress plugin versions before 2.3.3 allows remote attackers to execute arbitrary SQL commands via unspecified vectors in the plugin's database queries.
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< 2.3.3CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Locate the Easy Digital Downloads plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'easy-digital-downloads' or check via WordPress admin under Plugins > Installed PluginsAffected if The plugin folder does not exist - you are not affected. If it exists, continue to next check.
-
Identify the installed plugin versionOpen the main plugin file (usually easy-digital-downloads/easy-digital-downloads.php or readme.txt) and locate the version header defined in the plugin metadataAffected if You need the exact version number to compare against the affected range.
-
Compare the version against the vulnerable rangeThe affected versions are any version before 2.3.3. Check if your installed version is less than 2.3.3 (e.g., 2.3.2, 2.3.1, 2.2.x, etc.)Affected if If the version is below 2.3.3, your environment is affected by this SQL injection vulnerability.
-
Verify the plugin is activeCheck WordPress admin under Plugins > Installed Plugins to confirm the Easy Digital Downloads plugin status is 'Active'Affected if Only an active installation of a vulnerable version is at risk. An installed but deactivated plugin is not affected.
You are affected if Easy Digital Downloads is active with a version number lower than 2.3.3.
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.
dbcve · scoped2.3.3
Update the easy-digital-downloads plugin to version 2.3.3 or later to patch the SQL injection vulnerability.
Easy Digital Downloads 2.3.3
- Backup your WordPress database and files before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Find Easy Digital Downloads in the plugin list
- Click 'Update now' when an update to version 2.3.3 or later is available
- Alternatively, update via WP-CLI: wp plugin update easy-digital-downloads
- After updating, verify the plugin version shows 2.3.3 or higher in the plugins list
- Test critical e-commerce functionality (downloads, checkout, payment processing) to ensure the update did not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2015-9324 — 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-2015-9324 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