Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress sites running Neuronet theme
-
DeliverySend crafted request with traversal payload
-
ExploitTheme passes parameter into PHP include()
-
ExecutionVulnerable file or attacker-controlled content loaded
-
PersistRead wp-config.php or execute injected PHP
-
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 | Exploitation requires the WordPress site to be running the ThemeREX Neuronet theme at a version below 1.14.0 and have the vulnerable theme endpoint reachable over HTTP/HTTPS without authentication - consistent with PR:N/UI:N. The CVSS AC:H rating indicates additional non-default conditions are needed for full impact: based on CWE-98 and the C:H/I:H/A:H rating, the attacker likely needs the PHP runtime to be configured in a way that permits inclusion of files the attacker can influence (e.g., allow_url_include=On for remote inclusion, or a writable path such as an uploads directory whose location is predictable, or accessible log/session files for a log-poisoning style chain). Pure information disclosure of static files within open_basedir is the lower-bound impact; escalation to code execution depends on filesystem layout and PHP configuration, which is what makes attack complexity High rather than Low. |
| Impact | CVSS 3.1 base score is 8.1 (High) with vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - network reachable, no authentication, no user interaction, but high attack complexity and full CIA impact. The Patchstack reporter classifies this as Local File Inclusion (Information Disclosure), but the C:H/I:H/A:H profile implies the analyst believed file inclusion could escalate to code execution (e.g., by including a log or uploaded file) under the right conditions, which is consistent with AC:H. No EPSS, KEV, or POC signals are provided, so real-world exploitation pressure appears low at present; however, WordPress themes are mass-deployed and historically attract automated scanning once a Patchstack write-up lands. Conflicting signal worth noting: the vendor-supplied tag set lists only 'Information Disclosure' while the CVSS impact metrics claim full integrity and availability impact - defenders should verify with the Patchstack advisory whether RCE is actually achievable or whether the impact metrics are overstated. |
| Exploit ScenarioDerived | An unauthenticated attacker scans the internet for WordPress sites running the Neuronet theme, then issues a crafted HTTP request to a vulnerable theme endpoint with a traversal payload in a parameter that is reflected into a PHP include() call, reading sensitive files such as wp-config.php to recover database credentials and authentication keys. If the deployment also allows attacker-controlled content to be written to a known on-disk location (uploads, log entries, session files), the same inclusion primitive can be chained into PHP code execution under the web server account. No public exploit identified at time of analysis, so any attack would currently require independent vulnerability research against the patched diff. |
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 Neuronet WordPress theme before version 1.14.0 allows remote attackers to coerce the PHP runtime into including arbitrary files via untrusted input reaching an include/require statement. The flaw is reachable without authentication or user interaction, but CVSS marks attack complexity as High, suggesting non-trivial preconditions for full exploitation. No public exploit identified at time of analysis, and the issue is not on the CISA KEV list.
RemediationAI
Upgrade the Neuronet theme to version 1.14.0 or later, which Patchstack identifies as the fixed release; the advisory at https://patchstack.com/database/wordpress/theme/neuronet/vulnerability/wordpress-neuronet-theme-1-14-0-local-file-inclusion-vulnerability is the authoritative reference. If immediate patching is not possible, place a WAF rule (Patchstack, Wordfence, or ModSecurity) in front of the site to block requests containing path traversal sequences (../, ..%2f, php://, file://) targeting theme PHP endpoints, accepting the trade-off that legitimate parameters carrying dots or slashes may be blocked. As a stronger compensating control, temporarily switch the active theme to a default WordPress theme (Twenty Twenty-Four/Five) until the upgrade can be staged - this fully removes the vulnerable code path but breaks the site's appearance and any theme-specific shortcodes. Hardening php.ini with allow_url_include=Off and open_basedir restrictions further limits the blast radius if inclusion of remote or out-of-webroot files is attempted.
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
Neuronet is a commercial WordPress theme published by ThemeREX (CPE cpe:2.3:a:themerex:neuronet). The root cause is CWE-98, improper control of filename for an include/require statement in a PHP program, in which user-controlled input (typically a request parameter) is concatenated into a PHP include path. In WordPress themes this pattern frequently appears in template loaders, AJAX handlers, or shortcode renderers that resolve a template name from $_GET/$_POST without normalizing the path or restricting it to a whitelist, allowing traversal sequences or alternate stream wrappers to load attacker-chosen files served by the host filesystem.
Know when Neuronet 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 LFI in a WordPress theme justifies AV:N/PR:N/UI:N; AC:H reflects PHP/config preconditions for impact beyond file read; C:H for arbitrary file disclosure, I/A:L since RCE escalation is conditional.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
Lifecycle Timeline
1DescriptionCVE.org
Unauthenticated Local File Inclusion in Neuronet < 1.14.0 versions.
Executive ViewAI
The ThemeREX Neuronet WordPress theme has a critical security flaw that enables remote attackers to access sensitive server files including database credentials and configuration data without requiring authentication. This threatens any organization running WordPress with this theme and creates direct exposure to data breach and system compromise. Absence of a vendor patch means immediate alternative measures are essential.
No vendor-released patch identified at time of analysis. Mitigations: (1) Disable vulnerable theme immediately; (2) Implement Web Application Firewall rules blocking path traversal and file inclusion patterns; (3) Restrict web server file system access permissions; (4) Monitor server logs for suspicious file access attempts; (5) Verify sensitive configuration files are outside web root or protected by strict access controls.
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-210218
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB