Easy Digital DownloadsWordPress extension · Awesomemotive
CVE-2024-5057
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Easy Digital Downloads allows SQL Injection.This issue affects Easy Digital Downloads: from n/a through 3.2.12.
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 confidenceSQL injection vulnerability in Easy Digital Downloads WordPress e-commerce plugin allows attackers to inject malicious SQL commands through unsanitized user input in database queries, potentially enabling unauthorized data access, modification, or deletion.
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
<= 3.2.12CVSS 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 installed Easy Digital Downloads versionIn WordPress admin dashboard, go to Plugins > Installed Plugins > Easy Digital Displays. The version number is displayed below the plugin name. Alternatively, check the plugin header in /wp-content/plugins/easy-digital-downloads/easy-digital-downloads.php for the 'Version' comment.Affected if The displayed version is 3.2.12 or lower.
-
Confirm the plugin is activeIn WordPress admin, verify that Easy Digital Downloads is listed as an active (not deactivated) plugin on the Plugins page.Affected if The plugin is currently active and the version is 3.2.12 or lower.
-
Check WordPress database query logsReview WordPress debug logs (wp-content/debug.log if debugging is enabled) or server access/error logs for suspicious SQL queries containing unexpected characters, UNION statements, or OR clauses that may indicate SQL injection attempts targeting this plugin.Affected if Log analysis reveals SQL injection payloads or unusual database queries originating from plugin-related requests.
-
Audit custom code additionsReview any custom code, add-ons, or extensions created for Easy Digital Downloads, specifically examining any custom database query implementations that may interact with the plugin's data structures.Affected if Custom code uses unsanitized user input in SQL queries without prepared statements.
A user is affected if Easy Digital Downloads plugin version 3.2.12 or lower is installed and active in their WordPress environment.
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 dataUpgrade Easy Digital Downloads to the latest patched version and audit code for other potential SQL injection points; implement parameterized queries (prepared statements) and input validation for all database interactions.
Fix this in Easy Digital Downloads
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5057 — 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-2024-5057 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