Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege account
-
DeliverySend crafted request with malicious filename parameter
-
ExploitBypass path validation in theme include
-
ExecutionPHP include/require dereferences local file
-
PersistDisclose sensitive files (wp-config.php)
-
ImpactOptionally chain to code execution
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 an authenticated session with at least low-level privileges on the target WordPress site (CVSS PR:L), so anonymous/unauthenticated abuse is not indicated by the available data. The specific prerequisite is reaching the Billey theme code path that passes attacker-influenced input into a PHP include/require statement; the target must be running Billey version 2.1.8 or earlier. Exploitation is further limited by high attack complexity (AC:H), meaning success depends on non-trivial conditions such as precise payload/path construction rather than a single trivial request. No user interaction is required (UI:N). The vulnerability is scoped to the Billey theme, so sites not running this theme are unaffected. |
| Impact | The signals are mixed and warrant careful triage. The provided CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N) describes a network-reachable but high-complexity attack requiring low-level authentication - meaning the attacker already needs a valid, if limited, account on the WordPress site, and exploitation is non-trivial. The reported base score of 7.5 is elevated largely by the C:H/I:H/A:H impact triad, which is generous for a vulnerability the Patchstack tags characterize primarily as 'Information Disclosure / LFI'; a pure LFI's realistic impact is weighted toward confidentiality. No EPSS score, no KEV listing, and no POC were provided, so there is no evidence of active or imminent widespread exploitation. Net assessment: a legitimate but moderate-priority issue - the authentication requirement (PR:L) and high attack complexity (AC:H) meaningfully limit real-world exploitability, so it ranks below unauthenticated, low-complexity theme/plugin flaws. Note the tension: CWE-98 is nominally 'Remote File Inclusion' yet the description explicitly states Local File Inclusion - verify the true inclusion behavior with the vendor advisory before assuming remote-URL inclusion is possible. |
| Exploit ScenarioDerived | An attacker who holds or obtains a low-privilege authenticated WordPress account on a site running Billey <= 2.1.8 crafts a request to the vulnerable theme endpoint supplying a manipulated filename parameter that resolves to a sensitive local file (e.g., wp-config.php), causing the PHP include to disclose database credentials and secret keys. Given AC:H, the request likely requires specific parameter shaping or state to succeed, and under conditions permitting inclusion of attacker-controlled log or upload content it could be chained toward code execution. No public exploit is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 13, 2026
Local File Inclusion in the ThemeMove 'Billey' premium WordPress theme (versions up to and including 2.1.8) lets an authenticated attacker with low privileges control a filename used in a PHP include/require statement, exposing sensitive server-side files such as wp-config.php. Classified by Patchstack under CWE-98 (PHP Remote File Inclusion) but resolving to Local File Inclusion in practice, the flaw carries a CVSS 7.5 rating and no public exploit identified at time of analysis. Under specific conditions PHP file inclusion can escalate from information disclosure toward code execution via techniques such as log poisoning.
RemediationAI
No vendor-released patch version is identified in the available data - the record states the issue affects Billey through <= 2.1.8 without naming a fixed release, so administrators should consult the Patchstack advisory (https://patchstack.com/database/Wordpress/Theme/billey/vulnerability/wordpress-billey-theme-2-1-8-local-file-inclusion-vulnerability?_s_id=cve) and the ThemeMove changelog for a version above 2.1.8 and upgrade to it as the primary fix once released. Until a patched version is confirmed, apply compensating controls: place a Web Application Firewall (Patchstack, Wordfence, or equivalent) with rules blocking path-traversal and PHP-wrapper payloads in front of the site (trade-off: virtual patching may miss novel encodings); tighten account provisioning so that low-privilege roles capable of reaching the vulnerable code path are minimized or removed (trade-off: may restrict legitimate contributor workflows); and set PHP hardening directives such as open_basedir to constrain includable paths and disable allow_url_include/allow_url_fopen to prevent any remote-inclusion escalation (trade-off: may break plugins that legitimately fetch remote resources). Monitor web logs for suspicious include parameters and traversal sequences.
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
Billey is a commercial WordPress theme distributed by ThemeMove and built on PHP. The root cause is CWE-98, Improper Control of Filename for Include/Require Statement, where user-influenced input reaches a PHP include(), require(), include_once(), or require_once() call without adequate validation or allow-listing. Because the resolvable path is constrained to the local filesystem here, the outcome is Local File Inclusion rather than true remote inclusion - an attacker supplies a path (potentially with traversal sequences) that the theme dereferences and parses as PHP. The single CPE, cpe:2.3:a:thememove:billey:*:*:*:*:*:*:*:*, confirms the affected component is the Billey application/theme across all versions in scope.
Know when PHP 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:L/UI:N/S:U/C:H/I:H/A:H
Authenticated low-priv access (PR:L) and non-trivial path construction (AC:H); LFI primarily discloses sensitive files (C:H) with only conditional integrity impact (I:L) and no availability effect.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeMove Billey billey allows PHP Local File Inclusion.This issue affects Billey: from n/a through <= 2.1.8.
Executive ViewAI
The Billey WordPress theme (v2.1.8 and earlier) allows authenticated users with standard roles to read sensitive server files including database credentials via Local File Inclusion. No public exploit identified at time of analysis, but exposure of wp-config.php creates immediate risk of credential theft and database compromise for any organization using this theme.
No vendor-released patch identified at time of analysis. Interim mitigations: deploy WAF rules blocking wp-config.php and path traversal patterns; restrict low-privilege user account creation; relocate wp-config.php outside the web root if server architecture permits; monitor PHP error logs and file access logs for exploitation indicators; disable theme until patch becomes available.
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.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
EUVD-2026-43405
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB