Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress sites running Right Way theme
-
DeliverySend crafted unauthenticated HTTP request to theme endpoint
-
ExploitCoerce PHP include of attacker-chosen local file
-
ExecutionRead wp-config.php or invoke PHP wrapper
-
PersistExecute arbitrary PHP as web user
-
ImpactPivot to database credentials and site takeover
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 target WordPress site must have the Themeum Right Way theme installed and active at version ≤ 4.0, with the vulnerable PHP file include endpoint reachable over the network (default for any public WordPress front end). No WordPress account or user interaction is required (PR:N/UI:N). Limiting factors per CVSS AC:H: exploitation depends on conditions outside the attacker's control - likely a specific request shape, parameter name, or PHP stream wrapper / configuration (e.g. allow_url_include, open_basedir) - meaning hardened PHP installations or sites where the vulnerable include path is not triggered in the request flow may not be exploitable. Patchstack's description does not enumerate the exact parameter, so the precise trigger conditions are not independently confirmed from the available data. |
| Impact | Signals are mixed. CVSS 3.1 of 8.1 (AV:N/AC:H/PR:N/UI:N/C:H/I:H/A:H) reflects an unauthenticated network-reachable flaw with full CIA impact, but AC:H indicates non-trivial conditions (likely a specific parameter, request shape, or wrapper requirement) that reduce mass-exploitation potential. No EPSS, KEV, or SSVC data was provided in the input, and no public POC was referenced - exploitation status is therefore 'no public exploit identified at time of analysis.' The Patchstack tagging as LFI plus CWE-98 (which is typically RCE-class) suggests the realistic worst case is code execution, not just file disclosure, so any internet-exposed WordPress site running this theme should treat it as a high priority despite the absence of active-exploitation evidence. Missing data to flag: no fix version, no EPSS, no KEV entry, no independent advisory beyond Patchstack. |
| Exploit ScenarioDerived | An attacker scans WordPress sites for the Right Way theme by fingerprinting /wp-content/themes/rightway/ assets, then sends a crafted unauthenticated HTTP request whose parameter coerces a theme PHP script to include an attacker-controlled or sensitive local file (for example reading wp-config.php to steal database credentials, or chaining a PHP filter/log-poisoning wrapper to execute arbitrary PHP). No public POC has been identified at time of analysis, and the CVSS AC:H rating suggests the attacker must satisfy a specific parameter or wrapper condition for the include to succeed. |
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 Themeum Right Way WordPress theme versions 4.0 and earlier allows remote attackers to include arbitrary local files and likely achieve code execution through PHP file inclusion (CWE-98). The flaw is network-reachable without credentials, though CVSS records high attack complexity (AC:H), and no public exploit has been identified at time of analysis. The advisory is sourced from Patchstack's WordPress vulnerability database.
RemediationAI
No vendor-released patch identified at time of analysis; the Patchstack record covers versions ≤ 4.0 without naming a fixed release, so administrators should monitor https://patchstack.com/database/wordpress/theme/rightway/vulnerability/wordpress-right-way-theme-4-0-local-file-inclusion-vulnerability and the Themeum vendor channel for an updated version above 4.0 and upgrade as soon as one is published. In the interim, deactivate and remove the Right Way theme if it is not in active use, or switch the site to a different theme - this is the only fully effective mitigation. Compensating controls while the theme remains live: deploy a WAF rule (Patchstack, Wordfence, or ModSecurity) that blocks requests containing path-traversal sequences (../, %2e%2e, php://, data://, phar://) targeting theme endpoints under /wp-content/themes/rightway/, accepting that legitimate template parameters may be blocked; restrict PHP open_basedir and disable allow_url_include in php.ini to limit traversal scope, at the cost of breaking plugins that legitimately use stream wrappers; and place the WordPress instance behind authenticated access (HTTP basic auth or IP allow-listing on the front end) until a fix ships.
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
Right Way is a commercial WordPress theme distributed by Themeum (CPE cpe:2.3:a:themeum:right_way). The root cause is CWE-98 - Improper Control of Filename for Include/Require Statement in PHP, in which user-controlled input is passed into PHP include/require constructs without proper validation or allow-listing. In a WordPress theme this typically manifests as a parameter (e.g. page, file, template) consumed by a theme PHP file that resolves filesystem paths, enabling traversal to sensitive files such as wp-config.php or, depending on PHP configuration and wrappers (php://filter, data://, phar://), local-to-remote code execution. Because the theme code runs in the WordPress request lifecycle, exploitation does not require WordPress authentication.
Know when Right Way 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 WordPress endpoint with no auth or interaction (AV:N/PR:N/UI:N); AC:H reflects specific parameter/wrapper conditions; CWE-98 LFI typically yields full CIA impact via code execution.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in Right Way <= 4.0 versions.
Executive ViewAI
The Themeum Right Way WordPress theme (versions 4.0 and earlier) contains an unauthenticated remote file inclusion vulnerability (CVSS 8.1) that enables attackers to read arbitrary server files and execute code without credentials. Any organization running WordPress sites with this theme faces immediate risk of website takeover, data theft, and malware injection. No vendor patch is available, making rapid mitigation essential.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Immediately deactivate the vulnerable theme; (2) Deploy WAF rules blocking ../ patterns and parameter-based PHP file inclusion; (3) Implement Web server restrictions limiting access to sensitive directories (.php execution in upload folders); (4) Enable request logging and alerting for file inclusion indicators; (5) Maintain secure offline backups to enable recovery if compromise occurs; (6) Restrict WordPress admin access to known IP ranges.
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-37653
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB