Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconIdentify WordPress site running Mission theme
-
DeliveryProbe theme endpoint for vulnerable include parameter
-
ExploitSend crafted traversal or PHP wrapper payload
-
InstallRead wp-config.php and sensitive files
-
C2Forge admin session using leaked keys
-
ExecuteUpload backdoor plugin
-
ImpactAchieve persistent 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 | The affected site must have the ThemeREX Mission WordPress theme (versions ≤ 1.22) installed AND activated - sites with the theme present but inactive are not exposed because WordPress only loads PHP from the active theme. The vulnerable include endpoint must be reachable over HTTP/HTTPS without authentication (consistent with PR:N), and the attacker must craft a request that bypasses whatever sanitization the theme applies (the AC:H rating implies non-trivial conditions such as a specific parameter name, traversal encoding, or PHP stream wrapper). To escalate LFI to code execution, the server must additionally permit log poisoning, /proc/self/environ access, or PHP wrappers like php://filter - hardened PHP installations with open_basedir restrictions or allow_url_include=Off significantly limit impact. |
| Impact | The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/C:H/I:H/A:H, 8.1 High) reflects an unauthenticated network-exploitable issue with high triad impact but elevated attack complexity, suggesting non-trivial conditions (path traversal filtering, specific parameter, or null-byte/wrapper tricks) must be satisfied. EPSS and KEV data are not provided in the input; this CVE is not flagged as actively exploited. No public exploit is identified at time of analysis. Real-world risk is meaningful because WordPress themes are mass-deployed and Patchstack-tracked issues frequently see opportunistic scanning, but the AC:H rating and lack of public PoC argue against treating this as an emergency on par with PR:N/AC:L file-inclusion flaws - prioritize patching, but it is not a drop-everything event absent additional exploit intelligence. |
| Exploit ScenarioDerived | An unauthenticated attacker scans the public internet for WordPress sites running the Mission theme and sends a crafted HTTP request to the vulnerable theme parameter containing a traversal payload (e.g., ../../../../wp-config.php or php://filter/convert.base64-encode/resource=wp-config.php) to retrieve database credentials and WordPress secret keys. With wp-config.php exfiltrated, the attacker authenticates to the database or forges cookies via the leaked AUTH_KEY/SECURE_AUTH_KEY values to escalate to administrator and deploy a backdoor. The AC:H rating implies the attacker must first overcome an input filter or guess a specific endpoint, so this is more likely targeted than mass-exploited. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 16, 2026
Unauthenticated Local File Inclusion affects the ThemeREX Mission WordPress theme in all versions up to and including 1.22, enabling remote attackers to coerce the PHP application into including arbitrary local files. Exploitation can lead to sensitive file disclosure, source-code exposure, and - depending on what files are accessible on the server - remote code execution via log poisoning or PHP wrapper abuse. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
RemediationAI
No vendor-released patched version is identified in the available data - the Patchstack record covers versions through 1.22 without naming a fixed release, so site operators should consult the Patchstack advisory (https://patchstack.com/database/wordpress/theme/mission/vulnerability/wordpress-mission-theme-1-22-local-file-inclusion-vulnerability) and ThemeREX's vendor channel for an updated build above 1.22 and upgrade as soon as one is published. As compensating controls until a patch is confirmed, deploy a WAF rule that blocks path-traversal sequences (../, ..%2f, php://, file://, data://) and null bytes against requests reaching theme PHP endpoints; restrict PHP's open_basedir and disable allow_url_include and allow_url_fopen in php.ini to neutralize remote wrapper abuse (side effect: may break plugins that fetch remote resources); and consider switching to an alternate theme if the vendor does not respond - note that theme replacement requires layout re-validation. Patchstack subscribers can apply the vPatch as an immediate virtual mitigation.
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 flaw is classified as CWE-98 (Improper Control of Filename for Include/Require Statement in PHP), the canonical root cause for PHP file inclusion bugs. The affected component (CPE cpe:2.3:a:themerex:mission) is a commercial WordPress theme distributed by ThemeREX, meaning the vulnerable code lives in a theme template or AJAX handler that passes attacker-controlled input into a PHP include/require call without proper sanitization or path constraints. Because WordPress themes load within the main PHP request lifecycle, an LFI in a theme inherits the privileges of the web server process and the full WordPress configuration context (wp-config.php, database credentials, secret keys).
Know when Mission 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
Unauthenticated network-reachable LFI (AV:N, PR:N, UI:N); AC:H reflects filter/wrapper bypass implied by the vendor rating; full triad impact since LFI commonly enables config disclosure and RCE.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in Mission <= 1.22 versions.
Executive ViewAI
ThemeREX Mission WordPress theme (versions ≤1.22) is vulnerable to unauthenticated file access attacks; no public exploit has been identified, but the lack of vendor patch and the theme's widespread deployment create critical organizational risk of data breach and system compromise. The vulnerability's severity and patch status necessitate urgent remediation.
Deploy Web Application Firewall (WAF) rules restricting access to theme file paths; enforce restrictive file-system permissions to minimize exposed files; implement real-time monitoring of web server access logs for anomalous file-access patterns; conduct comprehensive immediate audit of file access on affected servers.
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-210209
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB