dbcve.org
Ebook StoreWordPress extension · Shopfiles

CVE-2024-6567

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-02
Fix available
A fix is available. Upgrade to after 5.8001 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Full Path Disclosure in all versions up to, and including, 5.8001. This is due to the plugin utilizing fpdi-protection and not preventing direct access to test files that have display_errors set to true. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website. The plugin vendor removed the test files, however, did not increment the version meaning this is inadequately patched in the same version that is affected.

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 test files from the fpdi-protection library that expose the full server path when accessed directly with PHP's display_errors enabled. Unauthenticated attackers can request these test files to retrieve absolute paths, aiding in reconnaissance for secondary attacks.

MitigationDisable display_errors in production PHP configurations and verify with the vendor that a proper version-bumped patch has been released, as the current version 5.8001 contains an inadequate fix.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

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

  1. Confirm Ebook Store plugin is installed
    Access WordPress admin > Plugins > Installed Plugins and look for 'Ebook Store' or 'Shopfiles Ebook Store', or inspect the wp-content/plugins directory for the plugin folder
    Affected if The plugin is present in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin, click on the Ebook Store plugin to view version details, or open the main plugin PHP file and look for the Version header comment, or check the readme.txt file
    Affected if The installed version is 5.8001 or any version lower than 5.8001
  3. Locate fpdi-protection test files
    Browse the plugin directory structure for folders or files containing 'fpdi' or 'test' - typically found in vendor, library, or test subdirectories within the plugin
    Affected if Test files from the fpdi-protection library exist in the plugin directory
  4. Verify PHP display_errors setting
    Check php.ini for 'display_errors = On', or inspect .htaccess for php_flag display_errors on, or check wp-config.php for ini_set('display_errors', 1)
    Affected if PHP display_errors is set to enabled (On or 1)

A WordPress site running Ebook Store plugin version 5.8001 or lower that contains fpdi-protection test files and has PHP display_errors enabled is vulnerable to path disclosure via direct file access.

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

Disable display_errors in production PHP configurations and verify with the vendor that a proper version-bumped patch has been released, as the current version 5.8001 contains an inadequate fix.

Recommended fix Moderate confidence
  1. 1. Locate your PHP configuration file (php.ini) - common paths include /etc/php/?.?/apache2/php.ini or /etc/php/?.?/fpm/php.ini
  2. 2. Find the display_errors directive in php.ini
  3. 3. Set display_errors to 'Off' (display_errors = Off)
  4. 4. Restart your web server (Apache/Nginx) for the changes to take effect
  5. 5. Verify the setting is applied by creating a test PHP file with phpinfo() or checking error logs
  6. 6. Alternatively, add the following to your .htaccess file: php_flag display_errors off
  7. 7. Contact the plugin vendor to request a proper version increment (version 5.8002) so users can verify they have the patched files

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
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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