CVE-2025-32286
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 ApusTheme Butcher butcher allows PHP Local File Inclusion.This issue affects Butcher: from n/a through <= 2.40.
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 Butcher theme by ApusTheme contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is used in include/require statements without proper validation, allowing attackers to include and execute arbitrary PHP files from the server filesystem.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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.
-
Identify if Butcher theme is installedCheck the wp-content/themes/ directory for a folder named 'butcher' or similar variant. In the theme folder, locate style.css and read the 'Version:' header to find the installed version number.Affected if The Butcher theme by ApusTheme is installed and the version is older than the patched version that addresses input validation on file inclusion paths.
-
Locate PHP files that handle file inclusionSearch the theme directory for PHP files containing include, require, include_once, or require_once statements. Focus on files that accept dynamic input via $_GET, $_POST, or $_REQUEST parameters for the file path.Affected if The theme contains PHP files that use user-supplied parameters (such as 'file', 'path', 'template', or similar) directly in include/require statements without sanitization.
-
Verify if file inclusion is reachable without authenticationExamine the PHP files identified in step 2 to determine if the file inclusion logic is accessible to unauthenticated users. Check if the code is in publicly accessible files or requires admin-level access.Affected if The vulnerable file inclusion code can be triggered by unauthenticated users via HTTP requests without requiring login or elevated privileges.
-
Check for directory traversal patterns in requestsTest (in a non-production manner) whether the file inclusion parameter accepts directory traversal sequences like '../' or absolute paths. Review access logs for suspicious requests containing these patterns to the theme's PHP files.Affected if The file inclusion mechanism allows directory traversal characters or absolute file paths to be included, enabling attackers to access files outside the theme directory.
A system is affected if the Butcher theme is installed with a vulnerable version, contains PHP code that includes files based on user input without validation, and that code is accessible to unauthenticated users.
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.
From vendor dataUpgrade to a patched version of the Butcher theme that implements proper input validation on file inclusion paths, or apply a WAF rule to block directory traversal patterns in request parameters.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32286 — 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-32286 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