CVE-2026-27335
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-27335 is a high-severity PHP Remote File Inclusion (CWE-98) vulnerability. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-27335 is an Improper Control of Filename for Include/Require Statement in PHP Program vulnerability, classified as PHP Local File Inclusion (CWE-98), affecting the Ekoterra WordPress theme developed by AncoraThemes for NonProfit, Green Energy & Ecology sites. The flaw exists in versions from n/a through 1.0.0, where inadequate validation of filenames in PHP include/require statements allows attackers to include local files. It carries a CVSS v3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating high severity due to potential for significant impacts across confidentiality, integrity, and availability.
Unauthenticated attackers can exploit this over the network with high attack complexity and no user interaction required. Successful exploitation enables reading sensitive local files, potentially leading to disclosure of configuration data, source code, or other server files, and in some cases escalating to remote code execution if controllable files are included. The high impacts reflect the potential for data theft, modification, or denial of service on vulnerable WordPress installations running the affected theme.
The Patchstack advisory at https://patchstack.com/database/Wordpress/Theme/ekoterra/vulnerability/wordpress-ekoterra-nonprofit-green-energy-ecology-theme-theme-1-0-0-local-file-inclusion-vulnerability?_s_id=cve documents the vulnerability, recommending theme updates beyond version 1.0.0 where available or removal of the theme as primary mitigations to prevent exploitation.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-9608
Vulnerability Data
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…
more
Theme: from n/a through <= 1.0.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis can discover missing filename restrictions before deployment.
Validating all inputs before they reach include/require statements directly stops untrusted filenames from being used.
Enforcing access authorizations on resources limits what an included file can reach even if a bad name is supplied.
Information-flow rules can block the loading of external or unauthorized files into the PHP process.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices such as input validation and allow-listing of include paths directly prevent the weakness.
Hardened runtime configuration (e.g., allow_url_include=off) directly blocks RFI even if code is flawed.
Execution restrictions can prevent the remote payload from running, while eliminating the weakness reduces the need for such controls.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect RFI but does not prevent the weakness by itself.
Secure coding standards directly require whitelisting and sanitization of filenames used in include/require statements.