CVE-2024-54376
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Spider Themes EazyDocs eazydocs allows PHP Local File Inclusion.This issue affects EazyDocs: from n/a through <= 2.8.0.
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 · moderate confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Spider Themes EazyDocs plugin (versions up to and including 2.8.0). The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to manipulate file path parameters to read sensitive local files from the server.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if EazyDocs plugin is installedAccess WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the plugin directory (wp-content/plugins/eazydocs) for the main plugin file to confirm presenceAffected if EazyDocs by Spider Themes is found in the WordPress installation
-
Determine installed EazyDocs versionRead the plugin version from the plugin header in the main EazyDocs PHP file (typically eazydocs.php) or check via WordPress admin Plugins pageAffected if The installed version is 2.8.0 or lower
-
Locate vulnerable include/require statementsSearch plugin PHP files for include, require, include_once, or require_once statements that use parameters directly without sanitization (look for patterns like include($_GET['param'] or require($var) without basename() or validation)Affected if Any PHP file contains include/require statements using unsanitized user input from request parameters
-
Identify accessible entry pointsReview publicly accessible PHP files in the plugin that handle file path parameters (check for $_GET, $_POST, or $_REQUEST usage in include/require contexts)Affected if The vulnerable code is reachable via HTTP requests without authentication requirements
Your environment is affected if EazyDocs version 2.8.0 or lower is installed and the plugin exposes PHP include/require statements that use unsanitized request parameters to load files.
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.
From vendor dataUpgrade to a patched version of EazyDocs if available; otherwise, implement strict input validation using basename() and whitelist approaches on all include/require statements, and ensure all user-supplied parameters are sanitized before being used in file operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54376 — 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-54376 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