dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-7437

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The Ebook Store plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the ebook_store_save_form function in all versions up to, and including, 5.8012. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 confidence

The Ebook Store WordPress plugin (versions up to 5.8012) lacks file type validation in the ebook_store_save_form function, allowing unauthenticated attackers to upload arbitrary files to the server. This arbitrary file upload vulnerability enables remote code execution when malicious files (e.g., PHP shells) are uploaded and accessed.

MitigationUpdate the Ebook Store plugin to version 5.8013 or later which includes proper file type validation. If immediate update is not possible, consider disabling the plugin or implementing web application firewall rules to block unauthenticated file upload requests to the affected endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Ebook Store plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ebook Store' or check the wp-content/plugins/ directory for an 'ebook-store' folder
    Affected if The plugin folder exists in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, find the Ebook Store plugin in the plugins list and read the version number displayed beneath the plugin name, or check the main plugin file (e.g., ebook-store.php) for the 'Version' header comment
    Affected if The version is 5.8012 or lower (the vulnerable version range)
  3. Check for presence of the vulnerable upload function
    Inspect the plugin file containing 'ebook_store_save_form' function (typically in the main plugin file or includes folder) and look for the file upload handling code without file type validation
    Affected if The function exists and processes file uploads without validating file types against an allowed list
  4. Identify the upload endpoint accessibility
    Review WordPress AJAX actions (admin-ajax.php) and direct PHP files in the plugin for form submissions that trigger the vulnerable function, typically accessible without authentication
    Affected if The upload functionality is reachable without requiring logged-in user authentication
  5. Search for suspicious uploaded files
    Check the WordPress uploads directory (wp-content/uploads/) for files with executable extensions (.php, .phtml, .php5, .exe, .js) that were uploaded recently and are not part of legitimate media
    Affected if Unexpected executable files exist in the uploads directory, especially with names suggesting shells or malware

You are affected if the Ebook Store plugin is installed AND the version is 5.8012 or lower AND the vulnerable file upload function is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Ebook Store plugin to version 5.8013 or later which includes proper file type validation. If immediate update is not possible, consider disabling the plugin or implementing web application firewall rules to block unauthenticated file upload requests to the affected endpoint.

Recommended fix High confidence

Version 5.8013 or higher of the Ebook Store plugin for WordPress

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Ebook Store' plugin
  4. Click 'Update now' if an update is available, or manually upload version 5.8013 or higher from the WordPress plugin repository
  5. Verify the update completed successfully
  6. Confirm the new version number in the plugins list
Caveat Review plugin settings after upgrade as a precaution; no major breaking changes expected for this security patch

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7437 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7437 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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