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

CVE-2026-27335

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 AncoraThemes Ekoterra - NonProfit, Green Energy & Ecology Theme ekoterra allows PHP Local File Inclusion.This issue affects Ekoterra - NonProfit, Green Energy & Ecology Theme: from n/a through <= 1.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 · moderate confidence

The Ekoterra theme by AncoraThemes contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly used in include/require statements without adequate validation. This allows attackers to include arbitrary PHP files from the server, potentially leading to code execution.

MitigationImplement strict input validation using allowlists for file inclusion paths, avoid using user input directly in include/require statements, and disable allow_url_include in PHP configuration. If available, update to a patched version from the vendor.

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. Identify if Ekoterra theme is installed
    Check the theme directory for the Ekoterra theme. Look in wp-content/themes/ for a folder named 'ekoterra' or similar. Check theme/style.css or theme functions for the theme name and version declaration.
    Affected if The Ekoterra theme by AncoraThemes is present in the WordPress themes directory.
  2. Determine the theme version
    Open the theme's main stylesheet (style.css) or functions.php file and locate the Version: header comment. Compare this version number against any known affected version ranges from vendor release notes.
    Affected if The installed version falls within the range that contains the LFI vulnerability (check vendor documentation for specific version boundaries).
  3. Locate vulnerable include/require patterns
    Search the theme's PHP files (especially template files, shortcodes, and AJAX handlers) for patterns where include, require, include_once, or require_once is used with variables derived from request parameters (e.g., $_GET, $_POST, $_REQUEST) without sanitization. Look for patterns like 'include($_REQUEST["file"])' or similar.
    Affected if Code exists that directly uses unsanitized user input (GET/POST/REQUEST parameters) in include or require statements.
  4. Identify the vulnerable parameter
    Examine the identified include/require code to determine which specific $_GET, $_POST, or $_REQUEST parameter is being used. Common parameter names for file inclusion include 'file', 'path', 'template', 'page', or 'slug'. Note the exact parameter name and the file(s) that process it.
    Affected if A specific request parameter (such as 'file', 'path', or 'template') is used directly in an include/require without validation.
  5. Test if the vulnerable endpoint is accessible
    Determine if the PHP file containing the vulnerable code is accessible via web requests. Attempt a benign local file inclusion test (with proper authorization in a test environment only) using a known safe file path like /etc/passwd or a non-PHP file to confirm the parameter is processed.
    Affected if The vulnerable parameter can be controlled through HTTP requests and the code executes include/require with that input, allowing arbitrary file inclusion.

A user is affected if the Ekoterra theme is installed, the vulnerable version is in use, and the theme contains code that passes unsanitized user input directly to PHP include or require statements, allowing attackers to read or execute arbitrary local files.

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

Implement strict input validation using allowlists for file inclusion paths, avoid using user input directly in include/require statements, and disable allow_url_include in PHP configuration. If available, update to a patched version from the vendor.

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