dbcve.org
Ebook StoreWordPress extension · Shopfiles

CVE-2024-12262

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 via the 'step' parameter in all versions up to, and including, 5.8001 due to insufficient input sanitization and output escaping. 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 (versions up to 5.8001) contains a reflected XSS vulnerability in the 'step' parameter. Due to insufficient input sanitization and output escaping, unauthenticated attackers can inject arbitrary JavaScript via a crafted URL that tricks users into clicking.

MitigationUpdate the Ebook Store plugin to a version newer than 5.8001. If no update is available, temporarily disable the plugin or implement WAF rules to block malicious 'step' parameter values.

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. Locate the Ebook Store plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Ebook Store' (or 'Shopfiles Ebook Store'). The version number is displayed below the plugin name.
    Affected if The displayed version is 5.8001 or lower.
  2. Confirm the plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that Ebook Store shows as 'Active' under the plugin status.
    Affected if The plugin is active and the version is 5.8001 or lower.
  3. Check plugin files for step parameter handling
    Access your WordPress site files via FTP or file manager. Navigate to /wp-content/plugins/ebook-store/ and search for files handling the 'step' parameter (typically in main plugin files or endpoint handlers). Look for code that reads $_GET['step'] or $_REQUEST['step'] without sanitization.
    Affected if Code directly uses the 'step' parameter in output (echo, print, printf) without using functions like esc_html(), esc_attr(), or sanitize_text_field().
  4. Identify vulnerable URL patterns
    Examine the plugin to determine which PHP files handle frontend requests. Look for code that outputs the 'step' parameter value back to the user without escaping, often in forms, redirects, or error messages.
    Affected if The plugin outputs the 'step' parameter value in HTML/JS context without sanitization, making reflected XSS possible.

You are affected if the Ebook Store plugin version is 5.8001 or lower, the plugin is active, and the code handles the 'step' parameter without proper sanitization and escaping.

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 a version newer than 5.8001. If no update is available, temporarily disable the plugin or implement WAF rules to block malicious 'step' parameter values.

Recommended fix Moderate confidence

Version higher than 5.8001 (typically 5.8002 or later)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Ebook Store plugin
  4. Check if an update is available and update to the latest version (should be higher than 5.8001)
  5. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin

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-12262 — 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-12262 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