Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site running Mane theme
-
DeliveryCraft request with path traversal payload
-
ExploitTrigger LFI in vulnerable theme parameter
-
ExecutionUpload PHP webshell disguised as image
-
PersistInclude uploaded file via LFI parameter
-
ImpactExecute arbitrary PHP code on server
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 | Unauthenticated file disclosure via LFI requires only network access to a WordPress installation running Mane theme version 1.7 or earlier - no credentials or special configuration are needed, consistent with CVSS PR:N. Escalation to remote code execution requires the additional precondition that an attacker-controlled file containing PHP code is present on the server's filesystem at a known or guessable path; this is most commonly achieved by uploading a PHP payload disguised as an image through WordPress's native media library or a theme-provided upload form. Exploitation is constrained by the following factors: (1) the AC:H rating indicates that achieving RCE is not straightforward and requires the file-presence precondition to be met; (2) sites that restrict the media upload endpoint to authenticated users or disable it entirely close the primary RCE pathway; (3) PHP open_basedir restrictions, if enforced, limit which filesystem paths can be included; and (4) server-side execution of PHP must not be blocked for the directories containing uploaded files. Basic file disclosure (e.g., reading wp-config.php) is a lower-bar impact achievable without file upload, limited mainly by the attacker's ability to guess or infer valid server paths. |
| Impact | The CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects a high-severity but conditionally exploitable vulnerability: unauthenticated network access with full CIA impact is offset by the AC:H designation, which captures the requirement for a specific precondition - almost certainly the presence of an attacker-controlled file on the server filesystem. This CVE does not appear in the CISA KEV catalog and no EPSS data was included in the available intelligence, indicating no confirmed active exploitation at time of analysis; however, absence from KEV is not confirmation of safety. The LFI attack class against WordPress themes is extensively documented and tooled, meaning exploitation complexity in practice may be lower than AC:H implies for sites that accept unauthenticated file uploads. Even a mid-sized municipal IT team in zabrze managing a portfolio of WordPress sites should treat this as an urgent remediation, because the combination of unauthenticated access and potential full server compromise via a well-known attack chain is precisely the profile that opportunistic attackers exploit systematically. No POC code has been publicly identified, which modestly reduces near-term mass-exploitation risk but does not justify deferral. |
| Exploit ScenarioDerived | An unauthenticated attacker, informed by the public Wordfence advisory, identifies a WordPress site running the Mane theme and locates the LFI-vulnerable request parameter. The attacker first uploads a PHP webshell embedded in a file with an image extension through the site's WordPress media upload endpoint or any theme-provided upload form, then sends a crafted HTTP request that supplies the uploaded file's server-side path to the vulnerable include parameter. The server executes the embedded PHP code with the privileges of the web server process, granting the attacker an interactive shell. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
Local File Inclusion in the Mane WordPress theme (all versions up to and including 1.7) allows unauthenticated remote attackers to include and execute arbitrary server-side PHP files, with a realistic path to full remote code execution when file upload functionality is accessible. The CVSS 8.1 score with AC:H signals that the most severe impact - arbitrary code execution - depends on a specific precondition, most likely an attacker-controlled file already present on the server filesystem. No public exploit has been identified at time of analysis, though the LFI-to-RCE chain on WordPress is a well-understood and widely practiced attack class.
RemediationAI
No vendor-released patch has been identified at time of analysis; operators should monitor the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/a71e330e-8673-49b4-8c31-63771533476f and the ThemeForest product page at https://themeforest.net/item/mne-a-modern-portfolio-theme-for-creatives/21333576 for a patched release. The most effective immediate risk reduction is to deactivate the Mane theme entirely until a fix is available, switching to an unaffected theme. If deactivation is not feasible, restrict or disable unauthenticated file upload capabilities on the WordPress installation, which removes the primary RCE escalation path; note this does not eliminate the underlying file disclosure risk. Configure PHP's open_basedir directive to confine includable file paths to the WordPress document root, reducing the attacker's ability to traverse to sensitive files outside the web root. Deploy a WAF (such as Wordfence's own firewall) with LFI detection rules targeting path traversal sequences and PHP include payloads in request parameters. Monitor web server access logs for requests containing encoded path traversal strings (e.g., ../, %2e%2e%2f) directed at theme endpoints.
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 vulnerability is classified as CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program), the canonical PHP Local File Inclusion weakness. It arises when user-supplied input is passed unsanitized to PHP's include(), require(), or equivalent functions within the theme's codebase, allowing an attacker to redirect file inclusion to arbitrary server paths. The affected product is precisely identified by CPE cpe:2.3:a:elated-themes:mane:*:*:*:*:*:*:*:* - a premium portfolio-oriented WordPress theme by Elated Themes distributed via ThemeForest. WordPress's native media upload mechanism, or any upload form provided by the theme, creates a chaining opportunity: an attacker can upload a PHP payload disguised as an image file (since MIME validation on uploaded content is often incomplete), then trigger the LFI parameter to include that file by its server-side path, elevating from file disclosure to remote code execution. PHP's open_basedir and upload directory configurations are the primary technical gatekeepers that limit this chain.
Know when Mane 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
AC:H reflects the file-upload precondition required to escalate to RCE; PR:N is consistent with unauthenticated exploitation confirmed by description and CVSS source.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Mane theme for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.7. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
Executive ViewAI
The Mane WordPress theme (versions up to 1.7) contains a file inclusion vulnerability that can lead to complete server compromise when file upload capabilities are enabled. Affected WordPress installations face risk of unauthorized access, data theft, and business disruption. No security patch is currently available, requiring immediate manual mitigation to protect WordPress infrastructure.
Implement Web Application Firewall rules blocking directory traversal attempts (../); restrict file upload functionality to only essential use cases; enforce restrictive file system permissions on WordPress directories (chmod 755 for directories, 644 for files); monitor web server logs for suspicious file inclusion requests and ../patterns; disable PHP execution in upload directories via .htaccess or web server configuration; segment WordPress installations from other sensitive systems via network isolation.
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.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-65303
GHSA-h4m2-w2c9-4x9f
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB