dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-22476

HIGH · 8.1 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Elated-Themes Etchy etchy allows PHP Local File Inclusion.This issue affects Etchy: from n/a through <= 1.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 confidence

Local File Inclusion vulnerability in the Elated-Themes Etchy WordPress theme allows attackers to include arbitrary local PHP files via improper control of filename parameters in include/require statements. This can lead to exposure of sensitive local files or code execution if an attacker can upload or control included files.

MitigationUpdate Etchy theme to latest patched version; if unavailable, replace theme or implement strict input validation on file path parameters to prevent directory traversal and unauthorized file inclusion.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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 checks

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

  1. Confirm Etchy theme installation
    Check your WordPress themes directory (wp-content/themes/) for the presence of the 'etchy' or 'Etchy' theme folder. If using a child theme, also verify the parent theme reference.
    Affected if The Etchy theme folder exists in the WordPress themes directory.
  2. Identify Etchy theme version
    Open the theme's style.css file located in the Etchy theme folder and locate the 'Version:' header in the CSS comment block at the top. Alternatively, check version information in functions.php.
    Affected if The installed version is older than the patched version provided by Elated-Themes.
  3. Locate vulnerable include/require patterns
    Search the Etchy theme PHP files (particularly in includes, lib, or core directories) for include(), require(), include_once(), or require_once() statements that use variables in file paths without sanitization. Look for patterns like 'include($filename)' or 'require($path . $_GET["file"])'
    Affected if The theme contains include/require statements using unsanitized variable parameters that could accept file paths.
  4. Check for vulnerable parameter exposure
    Examine PHP files that handle file inclusion requests. Identify if any GET, POST, or REQUEST parameters are used directly in file paths without input validation. Common parameter names in LFI flaws include 'file', 'path', 'page', 'template', 'include', or 'load'.
    Affected if User-controlled parameters are passed directly to include/require functions without validation or path traversal protection.
  5. Review web server access logs
    Search your web server access logs (apache access_log, nginx access.log, or similar) for requests to the Etchy theme that contain suspicious path traversal patterns such as '../', '..\', or references to sensitive local files like '/etc/passwd', 'wp-config.php', or 'php://input'.
    Affected if Logs show requests to Etchy theme files with directory traversal sequences or attempts to include local system files.

Your environment is affected if the Etchy theme is installed and contains the vulnerable file inclusion code pattern that uses unsanitized user input in include/require statements, exposing local file contents or enabling code execution.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Etchy theme to latest patched version; if unavailable, replace theme or implement strict input validation on file path parameters to prevent directory traversal and unauthorized file inclusion.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

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