CVE-2026-57796
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 VLThemes Leedo leedo allows PHP Local File Inclusion.This issue affects Leedo: from n/a through <= 3.0.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 · high confidenceA PHP Local File Inclusion (LFI) vulnerability exists in VLThemes Leedo theme (version <= 3.0.0) where user-supplied input is improperly validated before being used in include/require statements. This allows attackers to traverse the filesystem and include arbitrary local PHP files, potentially exposing sensitive configuration files, credentials, or achieving code execution if certain conditions are met.
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 Leedo theme versionLocate the theme's style.css or theme.json file in the theme directory (typically wp-content/themes/leedo/) and check the version declarationAffected if Version is 3.0.0 or lower, indicating the theme is within the affected range
-
Find PHP file inclusion functions using user inputSearch the theme's PHP files (especially in templates, controllers, or core theme files) for patterns like include(), require(), include_once(), or require_once() where the path comes from $_GET, $_POST, or $_REQUEST parametersAffected if Any include/require statement uses unsanitized user-supplied input as all or part of the file path
-
Inspect the vulnerable parameter sourceExamine the identified include/require calls to determine which HTTP parameter (e.g., ?file=, ?template=, ?page=) controls the included file path, then verify whether the code applies any validation (basename(), whitelist, or strip traversal sequences) before the inclusionAffected if The parameter is directly used in the include/require without validation or sanitization, or validation can be bypassed using ../ sequences
-
Test directory traversal accessibilityIf the vulnerable parameter is identified, attempt to access it with a traversal pattern (e.g., ../../wp-config.php) via an HTTP request to confirm the parameter is reachable and the inclusion occursAffected if The application processes the traversal sequence and attempts to include the specified path, indicating the vulnerability is exploitable in the environment
-
Check for sensitive file exposureRequest common sensitive files through the vulnerable parameter, such as wp-config.php, configuration files, or other PHP files outside the theme directory, to confirm local file inclusion capabilityAffected if The server returns content from files outside the intended theme directory, confirming the LFI is active
Your environment is affected if the Leedo theme version is 3.0.0 or lower AND user-controlled input is passed to include/require statements without proper validation, allowing directory traversal to include arbitrary local 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 dataImplement strict input validation using a whitelist approach for allowed files, strip directory traversal sequences (../), use basename() on paths, and ensure all file inclusion paths are hardcoded or validated against a whitelist of permitted files.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57796 — 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-2026-57796 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