Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site using Resurs theme
-
DeliveryLocate vulnerable include parameter
-
ExploitSend crafted traversal request
-
ExecutionPHP includes attacker-chosen file
-
PersistDisclose wp-config.php or execute poisoned content
-
ImpactPivot to full site compromise
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 | Target site must be running the ThemeREX Resurs WordPress theme version 1.3 or earlier as an active or otherwise reachable theme exposing the vulnerable include sink over HTTP(S). Exploitation requires the attacker to identify and reach the specific theme parameter that feeds an include/require call, and the CVSS AC:H rating implies non-trivial preconditions such as crafting a traversal payload, defeating path normalization, or relying on server-side state (log/session files) to escalate from disclosure to code execution. No authentication or user interaction is required (PR:N/UI:N). Sites that have deactivated or replaced the Resurs theme are not exploitable. |
| Impact | The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.1) indicates a network-reachable, unauthenticated flaw with HIGH attack complexity and complete CIA impact - consistent with an LFI requiring some non-trivial preconditions (e.g., specific parameter manipulation or path traversal encoding). No EPSS score, KEV listing, or POC is provided in the input, so real-world exploitation pressure cannot be confirmed. The AC:H rating tempers the otherwise critical-looking score: while LFI in a WordPress theme is a well-understood attacker target, exploitation likely depends on traversal mechanics or server-side conditions rather than a trivial one-shot request. Patchstack involvement suggests responsible disclosure rather than observed in-the-wild abuse, and KEV/POC status is UNKNOWN from the available data. |
| Exploit ScenarioDerived | An unauthenticated attacker on the internet sends a crafted HTTP request to a vulnerable Resurs-theme endpoint, supplying a path parameter that traverses out of the theme directory to read wp-config.php and recover database credentials. With minor additional effort (e.g., log file poisoning or including a previously uploaded media file), the attacker escalates the LFI into PHP code execution under the web server account. No public exploit is identified at time of analysis, but the technique class is well documented for WordPress themes. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 17, 2026
Unauthenticated Local File Inclusion in the ThemeREX Resurs WordPress theme versions 1.3 and below allows remote attackers to include and execute arbitrary local files on the server. The flaw, tracked under CWE-98 (Improper Control of Filename for Include/Require), enables disclosure of sensitive files and potential code execution depending on server configuration. No public exploit identified at time of analysis, though Patchstack has confirmed the issue against the affected theme.
RemediationAI
No vendor-released patch identified at time of analysis - the input data does not include a fixed Resurs theme version. Site operators should consult the Patchstack advisory (https://patchstack.com/database/wordpress/theme/resurs/vulnerability/wordpress-resurs-theme-1-3-local-file-inclusion-vulnerability) for an updated release and apply it once available. As compensating controls, deactivate and replace the Resurs theme on production sites (the most reliable mitigation, with the trade-off of frontend redesign), deploy a WAF rule blocking suspicious traversal sequences (../, %2e%2e, php://, file://) on requests targeting theme paths (may produce false positives on legitimate URL-encoded parameters), and harden PHP by setting allow_url_include=Off and configuring open_basedir to constrain accessible paths (may break legitimate plugins that read outside webroot). Restrict file system permissions on wp-config.php and other secrets so a successful read still limits credential exposure.
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 rooted in CWE-98, improper control of filename for an Include/Require statement in PHP. The Resurs theme by ThemeREX (CPE cpe:2.3:a:themerex:resurs) appears to pass user-controlled input into a PHP include/require call without sufficient sanitization or allowlisting. WordPress themes commonly expose AJAX endpoints or template loader parameters that, when improperly validated, can be coerced into loading attacker-chosen paths. Depending on PHP configuration (allow_url_include, open_basedir) and the inclusion sink, this can range from sensitive file disclosure (wp-config.php, /etc/passwd) to full PHP code execution via log poisoning, session files, or uploaded content.
Know when Resurs 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-reachable unauthenticated LFI (AV:N/PR:N/UI:N); AC:H reflects traversal/encoding preconditions; full C/I/A impact since LFI can yield secrets and PHP code execution.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in Resurs <= 1.3 versions.
Executive ViewAI
The ThemeREX Resurs WordPress theme (version 1.3 and below) contains an unauthenticated local file inclusion vulnerability permitting remote attackers to read sensitive files and potentially execute arbitrary code without credentials. Any WordPress site using this theme faces immediate risk of data exposure and server compromise. Rapid identification and remediation of affected installations is critical to prevent exploitation.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Deploy WAF rules blocking file inclusion patterns and suspicious parameter values; (2) Configure web server and PHP permissions to restrict file access to web root only; (3) Immediately deactivate the vulnerable theme; (4) Monitor access logs and web server errors for attempted LFI exploitation. Enable detailed logging of file access attempts by the PHP process.
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-2025-210235
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB