Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site using Ambient theme ≤1.7
-
ExploitSend crafted request with manipulated file path parameter
-
ExecutionServer includes attacker-influenced local file
-
ImpactDisclose sensitive files or achieve code execution
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V5 - File Handling File inclusion prevention, allowlisting
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Command and Control The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The flaw is an unauthenticated Local File Inclusion (CWE-98) in the Ambient WordPress theme version 1.7 and earlier, reachable remotely over the network (AV:N, PR:N, UI:N). The specific vulnerable parameter, endpoint, or theme feature that passes user input into the PHP include/require path is NOT named in the supplied description and should be obtained from the Patchstack advisory. The key LIMITING factor is the vendor-assigned HIGH attack complexity (AC:H), indicating exploitation requires preconditions outside the attacker's control - likely a specific request path, server configuration, or state - rather than trivial constant-success exploitation. Exploitation is further bounded to sites actually running the Ambient theme at version ≤1.7; sites on other themes or a fixed version are unaffected. |
| Impact | The provided CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, score 8.1) describes a network-reachable, unauthenticated flaw with full CIA impact but HIGH attack complexity, which tempers real-world risk. No EPSS score, CISA KEV listing, or public POC is present in the supplied data, so exploitation status is 'no public exploit identified at time of analysis.' The AC:H metric is the single most important mitigating signal: it implies exploitation depends on conditions outside the attacker's control (specific configuration, timing, or non-trivial preconditions), which is consistent with many WordPress file-inclusion bugs that require a particular parameter path or theme feature to be reachable. There is a notable tension in the input: the CWE-98 classification and the 'Information Disclosure'/'LFI' tags point primarily at a file-read/confidentiality issue, yet the vendor vector asserts I:H and A:H - integrity and availability impact at HIGH is only justified if the inclusion can be escalated to code execution (e.g., log poisoning or inclusion of attacker-influenced PHP), which is not confirmed in the description. Treat the I:H/A:H as unverified and confirm with Patchstack. Overall this is a moderate-priority item: genuinely remote and unauthenticated, but gated by HIGH complexity and affecting a niche premium WordPress theme rather than ubiquitous infrastructure, so it does not warrant emergency-patch urgency absent evidence of active exploitation. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker crafts a request to a vulnerable Ambient theme endpoint that passes attacker-influenced input into a PHP include/require path, causing the server to read and return a local file (such as wp-config.php) or, if conditions allow, include attacker-controlled content. The HIGH attack complexity means the attacker must satisfy specific preconditions for the inclusion to succeed. No public exploit code is identified in the supplied data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Unauthenticated local file inclusion in the Ambient WordPress theme (Elated Themes) at version 1.7 and earlier lets remote attackers coerce the PHP template loader into reading files outside the intended theme path, exposing secrets such as wp-config.php, database credentials, and other server-side data that is echoed back in the response. The vendor vector (AV:N/AC:H/PR:N/UI:N, score 8.1) requires no authentication or user interaction, but the HIGH attack complexity signals a precondition outside the attacker's control must line up for exploitation, so this is not a trivial one-request compromise of every site; our reassessment retains the confidentiality impact while dropping the unconfirmed integrity and availability components. Exposure is limited to WordPress installations running Ambient at 1.7 or below, and no public exploit code has been identified at time of analysis.
RemediationAI
No vendor-released patch was identified at time of analysis; the only reference supplied is the Patchstack advisory at https://patchstack.com/database/wordpress/theme/ambient/vulnerability/wordpress-ambient-theme-1-7-local-file-inclusion-vulnerability, which should be checked for a patched Ambient release and for the specific vulnerable parameter before attempting parameter-level blocking. Until a fix is confirmed, the highest-value action is to deactivate and remove the Ambient theme from any site that does not require it, accepting the obvious side effect that the site loses its current design and must run a supported theme; for sites that must keep it, deploy WAF or reverse-proxy rules that reject requests containing traversal sequences (../, ..%2f, %252e%252e) or PHP wrapper strings (php://, php://filter, data://, phar://) in query strings, cookies and POST bodies, understanding that generic LFI signatures can false-positive on legitimate file paths and that obfuscation variants may slip through. Harden the PHP runtime so a successful inclusion is less damaging: keep allow_url_include=Off and allow_url_fopen=Off, set open_basedir to the WordPress document root and upload directory to prevent reads of /etc/passwd and other system files (at the cost of possibly breaking plugins that legitimately touch files outside that tree), run the web server user with least privilege, and rotate any credentials stored in wp-config.php if compromise is suspected. Finally, monitor web server and PHP logs for include-path traversal attempts and for anomalous access to theme PHP files, since detection is likely to precede any patch.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-98, improper control of filename for include/require statements in PHP, the canonical parent class underlying local file inclusion in PHP applications. WordPress themes are ordinary PHP code: template files such as header.php, footer.php and single.php are pulled into execution via include/require/require_once and get_template_part(), and any theme-supplied value (a query parameter, cookie, AJAX action argument, or path fragment) that reaches those calls without allow-list validation can be steered by an attacker using directory traversal (../../) or PHP stream wrappers such as php://filter/convert.base64-encode/resource= to read arbitrary local files readable by the web server user. The CPE entry cpe:2.3:a:elated-themes:ambient:*:*:*:*:*:*:*:* uses a version wildcard, so the source data flags every Ambient release rather than pinning 1.7, while the advisory scope is explicitly "<= 1.7" - treat 1.7 as the last known vulnerable release until Patchstack publishes a patched version. Tags from the source (PHP, Information Disclosure, LFI) align with an information-disclosure outcome rather than code execution, which is consistent with our assessment narrowing impact to confidentiality only. Notably, the description does not name the vulnerable parameter, file, or theme feature that feeds the include path; that detail must come from the Patchstack advisory and is the single most important missing input for precise detection and virtual patching, since the vendor's AC:H rating implies the successful request depends on hitting a specific path, state, or server configuration.
Know when Ambient gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Remote unauthenticated LFI (AV:N/PR:N/UI:N) with vendor-indicated preconditions (AC:H); confidentiality HIGH from file disclosure, but I/A set N as code-execution escalation is unconfirmed and tags indicate information disclosure.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in Ambient <= 1.7 versions.
Executive ViewAI
The Ambient WordPress theme from Elated Themes, versions 1.7 and earlier, contains a file-inclusion flaw that allows an unauthenticated remote attacker to read server-side files such as wp-config.php, exposing database credentials and other secrets. Any organization hosting WordPress sites on this theme should assume its site secrets are reachable by an attacker who can satisfy the exploit's preconditions, and because no vendor patch exists, leadership must treat containment and credential rotation as the primary near-term risk response. Sites running other themes or newer versions are not affected.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the Ambient theme (version 1.7 and earlier), block directory-traversal and file-inclusion request patterns at the WAF or reverse proxy, restrict filesystem permissions on wp-config.php, rotate database credentials and WordPress authentication salts, and monitor web server logs for LFI attempts pending replacement with a supported theme.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Local File Inclusion vulnerabilities occur when an application accepts user-controlled input to specify which file should be loaded or executed, typically through functions like PHP's `include()`, `require()`, or `fopen()`.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-96520
GHSA-x2pv-34vv-36qv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB