dbcve.org
Ebook StoreWordPress extension · Shopfiles

CVE-2024-11287

MEDIUM · 6.1 CVSS v3.1 Published 2024-12-21
Fix available
A fix is available. Upgrade to after 5.8001 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in all versions up to, and including, 5.8001. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

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 is vulnerable to reflected cross-site scripting (XSS) in versions up to 5.8001. The vulnerability stems from the use of WordPress add_query_arg() function without proper output escaping, allowing unauthenticated attackers to inject malicious JavaScript via crafted URLs that execute when users click malicious links.

MitigationUpdate the Ebook Store plugin to the latest version once available, or modify the code to properly escape add_query_arg() output using functions like esc_url() or esc_attr() before rendering.

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
Ebook StoreWordPress extension
Affected:<= 5.8001

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

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

  1. Check installed Ebook Store plugin version
    In WordPress admin, go to Plugins > Installed Plugins > locate 'Ebook Store' and check the version number displayed below the plugin name, or inspect the plugin header in /wp-content/plugins/ebook-store/readme.txt or the main plugin PHP file for the 'Version' tag.
    Affected if The displayed version is 5.8001 or lower.
  2. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins > verify that 'Ebook Store' shows an 'Active' status under the plugin name.
    Affected if The plugin is currently activated.
  3. Inspect plugin code for vulnerable add_query_arg usage
    Search the plugin directory (wp-content/plugins/ebook-store/) for instances of 'add_query_arg' that are not followed by 'esc_url', 'esc_attr', 'esc_html', or 'esc_js' when outputting to page. Common pattern: echo add_query_arg( ... ) without escaping functions.
    Affected if Unescaped add_query_arg output is found in the plugin PHP files.
  4. Check for unauthenticated query parameter handling
    Review the plugin's main PHP files for direct use of $_GET or $_REQUEST parameters that might be reflected in URLs without sanitization, particularly in admin.php or front-facing files.
    Affected if The plugin processes and outputs query parameters without proper sanitization.

You are affected if the Ebook Store plugin version is 5.8001 or lower and the plugin is active, with vulnerable unescaped add_query_arg code present in your installation.

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
Upgrade available Upgrade to a release after 5.8001
Interim mitigation

Update the Ebook Store plugin to the latest version once available, or modify the code to properly escape add_query_arg() output using functions like esc_url() or esc_attr() before rendering.

Recommended fix Moderate confidence

Version 5.8002 or later (check WordPress plugin repository for latest release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Ebook Store plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running version 5.8002 or higher

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

Fix this in Ebook Store Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11287 — 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-2024-11287 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