CVE-2024-13435
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 Ebook Downloader plugin for WordPress is vulnerable to SQL Injection via the 'download' parameter in all versions up to, and including, 1.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 Ebook Downloader WordPress plugin fails to properly escape the user-supplied 'download' parameter and lacks prepared statements in its SQL queries. This allows unauthenticated attackers to inject arbitrary SQL commands via the download parameter to extract sensitive data from the database.
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<= 1.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 plugin installation and versionNavigate to WordPress Admin > Plugins and locate 'Infoway Ebook Downloader' or check the plugin directory /wp-content/plugins/ for an ebook-downloader folder. View the plugin header to read the installed version number.Affected if The plugin is installed and the version is 1.0 or below.
-
Identify the vulnerable fileLocate the main plugin PHP file (commonly index.php or ebook-downloader.php in the plugin folder) and search for code handling the 'download' parameter and direct SQL queries without prepare() statements.Affected if The plugin file contains a 'download' parameter processed with unsanitized variables in SQL queries.
-
Check if the vulnerable endpoint is accessibleSend a test request to the affected page (typically the page where the download shortcode is placed) including a 'download' parameter with a simple test value (e.g., ?download=1). Use a Web Application Firewall or HTTP traffic logs to verify the request reaches the plugin.Affected if The page responds and the plugin processes the 'download' parameter without requiring authentication.
-
Review access logs for exploitation signsExamine web server access logs (Apache/nginx) for requests to pages using this plugin that contain SQL injection patterns in the 'download' parameter (e.g., UNION SELECT, OR 1=1, etc.).Affected if Log entries show SQL injection payloads submitted to the 'download' parameter.
Your environment is affected if the Infoway Ebook Downloader plugin version 1.0 or below is installed and the download functionality is accessible to unauthenticated 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.
dbcve · scopedUpdate to a patched version of the plugin if available; otherwise disable the plugin until a fix is released. Consider deploying a WAF rule to block SQL injection attempts as a temporary mitigation.
Latest version of Ebook Downloader plugin (check WordPress plugin repository for version newer than 1.0)
- Check the current version of the Ebook Downloader plugin installed on your WordPress site
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate Ebook Downloader and verify the current version number
- If the installed version is 1.0 or below, check for available plugin updates via Plugins > Add New > Upload or the WordPress plugin repository
- Update to the latest available version of Ebook Downloader that addresses this SQL injection vulnerability
- If no update is available from the WordPress plugin repository, consider using an alternative plugin or removing the plugin entirely until a patch is released
- Verify the update was successful and test the plugin functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13435 — 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-13435 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