BilleyWordPress extension · Thememove
CVE-2025-59558
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.6.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Billey theme by ThemeMove contains a PHP Local File Inclusion (LFI) vulnerability due to improper control of filename parameters in include/require statements. This allows attackers to read sensitive files on the server by manipulating file path references, potentially exposing configuration files, credentials, or source code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
BilleyWordPress extension
< 2.1.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Billey theme versionOpen the theme's style.css file (typically at /wp-content/themes/billey/style.css) and look for the 'Version:' field in the comment headerAffected if The version listed is lower than 2.1.6 (e.g., 2.1.5, 2.1.4, etc.)
-
Locate PHP files with dynamic file inclusionSearch the theme directory for PHP files containing include, require, include_once, or require_once statements that use variables (e.g., include($var), require($_GET['param']))Affected if Any PHP file in the theme uses include/require with unsanitized variables from $_GET, $_POST, or $_REQUEST
-
Identify exposed file inclusion parametersExamine the theme's PHP files for parameters that accept file paths (such as 'file', 'path', 'template', 'page', 'slug') passed via URL or form inputs and then used in include/require statementsAffected if Parameters accepting file paths are used directly in include/require without validation or sanitization
-
Check for LFI vulnerability patternsReview identified include/require code for patterns like: include($_GET['file']); require($page); include_once($_REQUEST['path']); or similar where user input flows directly to file inclusion functionsAffected if The code directly includes files based on user input without sanitizing the path (e.g., no basename(), no whitelist checks, no removal of directory traversal characters)
-
Verify vulnerability is exploitableTest if the file inclusion parameters accept directory traversal sequences like ../../ to access files outside the theme directoryAffected if The application allows reading PHP files outside the intended directory using ../ sequences in the parameter
You are affected if the Billey theme version is below 2.1.6 AND the theme exposes PHP files with include/require statements that use unsanitized user input to control which files are included.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.1.6
Update the Billey theme to version 2.1.6 or later. If immediate update is not possible, disable the theme and review server access logs for indicators of exploitation targeting include/require functionality.
2.1.6
- Upgrade the Billey theme to version 2.1.6 or later to remediate the PHP Local File Inclusion vulnerability (CWE-98).
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Billey
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59558 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59558 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data