Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site running AutoParts theme
-
DeliveryProbe theme endpoint with traversal payload
-
ExploitTrigger unsanitized PHP include
-
ExecutionRead wp-config.php or session files
-
PersistExtract DB credentials and secret keys
-
ImpactAchieve authenticated foothold or RCE
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 AutoParts WordPress theme (ThemeREX, versions ≤ 1.5.8) must be installed and active on the target WordPress site, with the vulnerable theme PHP endpoint reachable over the network - no authentication or user interaction is required per PR:N/UI:N. The AC:H qualifier indicates exploitation requires a non-trivial precondition, most likely a specific parameter format, wrapper (e.g., php://filter), or knowledge of a valid file path on the server's filesystem; this limits opportunistic scanning but does not prevent targeted exploitation. PHP configuration directives such as open_basedir restrictions or allow_url_include=Off do not block local inclusion but do constrain what files can be read. |
| Impact | The CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yields 8.1 (High), driven by network reach, no authentication, no user interaction, and full CIA impact - the AC:H qualifier suggests the attacker must satisfy some non-trivial condition (likely a specific parameter shape or wrapper). EPSS and CISA KEV status are not provided in the input, and no public PoC is referenced beyond the Patchstack advisory, so this is currently a high-CVSS issue without confirmed mass exploitation. However, LFI in WordPress themes is historically a high-value target because attackers can routinely chain it to disclose wp-config.php database credentials or achieve RCE via PHP wrappers and uploaded media, so defenders should treat it as a real priority rather than theoretical risk. |
| Exploit ScenarioDerived | A remote attacker crafts an HTTP GET request to a vulnerable AutoParts theme endpoint, supplying a path-traversal or php://filter payload in the parameter that flows into PHP's include/require call. The server returns the contents of wp-config.php, leaking database credentials and WordPress secret keys, which the attacker then uses to authenticate to the database or pivot to authenticated RCE via plugin upload. No public exploit identified at time of analysis, but the bug class is well-understood and trivial to weaponize once the vulnerable parameter is identified. |
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 AutoParts WordPress theme versions 1.5.8 and earlier allows remote attackers to include and execute arbitrary local files on the server. No public exploit identified at time of analysis, but the CWE-98 classification and PR:N CVSS vector make this a meaningful pre-authentication risk for any WordPress site running the theme. Successful exploitation typically leads to sensitive file disclosure (wp-config.php) and, when combined with log poisoning or uploaded content, full remote code execution.
RemediationAI
No vendor-released patch identified at time of analysis; monitor the Patchstack advisory (https://patchstack.com/database/wordpress/theme/autoparts/vulnerability/wordpress-autoparts-theme-1-5-8-local-file-inclusion-vulnerability) and the ThemeREX/Envato product page for a release above 1.5.8 and upgrade as soon as one is available. As compensating controls, deploy a WAF rule (Patchstack, Wordfence, or ModSecurity OWASP CRL rules 930100/930120) to block path-traversal sequences and php:// wrappers on requests to the theme's PHP endpoints, restrict open_basedir and allow_url_include=Off in php.ini to constrain what files PHP can include, and deny direct web access to wp-config.php and theme include directories at the web-server layer - note that aggressive path-traversal WAF rules can break legitimate query strings containing %2F or dot sequences, so test in detection mode first. If patching is not imminent, consider deactivating the AutoParts theme and switching to a default theme until a fix is shipped.
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
AutoParts is a commercial WordPress theme published by ThemeREX (CPE cpe:2.3:a:themerex:autoparts) and aimed at automotive parts retailers. The flaw is classified as CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program), the canonical PHP file-inclusion weakness in which user-controlled input reaches a require/include/include_once/require_once call without proper sanitization or allow-listing. In WordPress themes this pattern most often appears in AJAX handlers, shortcode renderers, or template-loader endpoints registered via admin-ajax.php or rewrite rules that accept a template/file parameter.
Know when Autoparts 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 theme endpoint, no auth or user interaction; AC:H reflects the non-trivial parameter/wrapper precondition; LFI to wp-config.php enables full CIA impact via DB takeover.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in AutoParts <= 1.5.8 versions.
Executive ViewAI
ThemeREX AutoParts WordPress theme (versions 1.5.8 and earlier) contains an unauthenticated Local File Inclusion vulnerability enabling attackers to extract sensitive data and achieve remote code execution on affected websites. Organizations running this theme face immediate risk of credential compromise, customer data breach, and full site takeover. No vendor patch is available.
No vendor-released patch identified at time of analysis. Interim mitigations: Immediately disable or remove the theme from all WordPress installations; implement WAF rules blocking ../ and file path traversal patterns; restrict web server file permissions on sensitive directories (wp-config.php, database files); enable comprehensive audit logging for file access attempts; maintain current WordPress core and security patches to reduce secondary exploitation vectors.
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-37654
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB