Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend unauthenticated HTTP request to WordPress
-
DeliveryInject path-traversal payload into vulnerable theme parameter
-
ExploitPHP includes arbitrary local file
-
ExecutionExfiltrate wp-config.php database credentials
-
PersistOptionally inject PHP into server log via crafted header
-
ImpactRe-include poisoned log to execute arbitrary code
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 | Exploitation requires no authentication (CVSS PR:N) and no user interaction (UI:N), meaning any unauthenticated HTTP client can attempt the attack against an internet-exposed WordPress installation running Shuffle theme version 1.8 or earlier. The CVSS AC:H metric indicates a specific complexity barrier must be overcome - this likely corresponds to a non-default PHP configuration, a precise knowledge of the vulnerable parameter name and acceptable path format, or a multi-step attack chain (e.g., log poisoning) to achieve the full high-impact outcome. The vulnerability is limited to sites where the Shuffle theme is active (not merely installed); deactivated themes are not served by WordPress. Exploitation is further constrained by the web server process's filesystem permissions - files outside the web root or owned by root with restrictive permissions may be unreadable even if the LFI path resolves. The AC:H barrier limits the realistic risk from mass-automated scanning, but targeted exploitation by a skilled attacker remains viable. |
| Impact | The CVSS 8.1 score reflects a high-severity finding driven by network accessibility (AV:N), no authentication requirement (PR:N), no user interaction (UI:N), and high confidentiality, integrity, and availability impact. The AC:H metric is the principal mitigating signal - it indicates that exploitation is not straightforward and likely requires specific conditions such as a precisely crafted payload, a particular server filesystem layout, or a secondary technique (e.g., log poisoning) to achieve the full C:H/I:H/A:H impact. EPSS data was not provided in the input, so exploitation probability cannot be quantified. No CISA KEV listing exists, and no public POC has been identified, which reduces the immediate weaponization risk. Defenders should treat this as high priority for WordPress sites running this theme, but the AC:H factor means mass-automated exploitation is less likely than for AC:L LFI variants. The combination of PR:N and AV:N means any internet-exposed WordPress installation running Shuffle <= 1.8 is within the attack surface. |
| Exploit ScenarioDerived | An unauthenticated attacker identifies a WordPress site running Shuffle theme 1.8 or earlier and sends a crafted HTTP GET or POST request containing a path-traversal payload targeting the vulnerable file-inclusion parameter, directing PHP to include a sensitive local file such as /var/www/html/wp-config.php. The retrieved file contents expose database credentials and secret keys, enabling lateral movement into the database or forging WordPress authentication cookies. Under configurations where web server logs are readable by PHP, the attacker may first inject PHP code into a log file via a crafted User-Agent header, then include that log to achieve remote code execution. No public POC has been identified at time of analysis, but the attack pattern is a well-understood LFI technique requiring moderate skill. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 20, 2026
Unauthenticated Local File Inclusion (LFI) in the Shuffle WordPress theme by Edge Themes affects all versions up to and including 1.8, allowing a remote attacker without any credentials to force the PHP application to include arbitrary local files from the server. Successful exploitation can expose sensitive files such as wp-config.php (containing database credentials) and, under certain server configurations, escalate to remote code execution via log poisoning or similar chaining techniques. No public exploit code or CISA KEV listing has been identified at time of analysis, though the CVSS 8.1 score and CWE-98 classification indicate a high-severity, high-impact path.
RemediationAI
The primary remediation is to update the Shuffle theme to a version beyond 1.8 once a patched release is confirmed available from Edge Themes - no exact fixed version number was provided in the available input data, so administrators should consult the vendor directly and the Patchstack advisory at https://patchstack.com/database/wordpress/theme/shuffle/vulnerability/wordpress-shuffle-theme-1-8-local-file-inclusion-vulnerability?_s_id=cve for the confirmed fix version. As an immediate compensating control, restrict public access to the WordPress installation via IP allowlist or Web Application Firewall rules that block path traversal sequences (e.g., ../, %2e%2e%2f, encoded dot-dot-slash variants) targeting the vulnerable parameter identified by Patchstack. Additionally, ensure PHP is configured with open_basedir restrictions to limit the file system paths accessible via include operations, which reduces the blast radius of any LFI exploitation. Disabling allow_url_include in php.ini prevents remote file inclusion chaining, though this does not eliminate local file inclusion. These controls carry trade-offs: WAF rules may produce false positives on legitimate theme requests; open_basedir restrictions may break other plugins or themes if misconfigured.
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
CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program) covers vulnerabilities where attacker-controlled input reaches a PHP include(), require(), or equivalent without adequate sanitization, enabling traversal to arbitrary local file paths. The affected product is the Shuffle theme (CPE: cpe:2.3:a:edge_themes:shuffle:*:*:*:*:*:*:*:*) - a commercial WordPress theme distributed by Edge Themes. WordPress themes execute in the PHP runtime context of the web server process and routinely handle URL or POST parameters that control template or asset loading; when these parameters are not properly sanitized, they can be weaponized as LFI vectors. The CVSS vector AV:N/AC:H indicates the vulnerability is reachable over the network but requires the attacker to overcome some complexity barrier - likely a specific parameter name, path encoding, or PHP configuration requirement such as a writable log path for chaining to RCE.
Know when Shuffle 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
Network-accessible LFI with no auth (AV:N, PR:N), but AC:H reflects complexity needed to achieve full RCE chaining for I:H/A:H impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in Shuffle <= 1.8 versions.
Executive ViewAI
The Shuffle WordPress theme (versions 1.8 and earlier) contains a high-severity unauthenticated vulnerability allowing attackers to access sensitive server files including database credentials. No public exploit identified at time of analysis, but the straightforward attack vector poses significant risk to WordPress installations using this theme.
No vendor-released patch identified at time of analysis. Interim mitigation requires: immediately disabling the vulnerable Shuffle theme and replacing it with an actively maintained alternative; deploying Web Application Firewall (WAF) rules to block path traversal attempts (../../../, encoded variants); restricting file system permissions to prevent PHP execution in sensitive directories; implementing intrusion detection signatures for LFI exploitation patterns; enforcing strict database access controls and IP whitelisting for database connections; and maintaining comprehensive access/error logs for forensic analysis. Complete theme replacement is the only reliable long-term control.
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.
Cross-tenant privilege escalation in Shuffle (self-hosted SOAR platform) through version 2.2.1 lets an administrator who
Local File Inclusion in Edge-Themes' Shuffle WordPress theme (all versions through 1.8) exposes WordPress installations
EUVD-2025-210754
GHSA-6fw2-rvrj-mw88
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB