CVE-2025-31060
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 Capie capie allows PHP Local File Inclusion.This issue affects Capie: from n/a through <= 1.0.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 · moderate confidenceLocal File Inclusion (LFI) vulnerability in the Capie theme allows attackers to manipulate file path parameters in PHP include/require statements to read sensitive files from the server. The vulnerability stems from improper validation of user-supplied input used in file inclusion functions.
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 Capie theme installation and versionLocate the theme's version file (typically version.php, style.css header, or theme.json in the theme directory) and note the installed version numberAffected if The installed Capie theme version is lower than 1.0.41 or the version cannot be determined
-
Locate file inclusion code in the themeSearch theme PHP files for include, require, include_once, or require_once statements that use variables in the file path (e.g., include($_GET['file']) or require($path) without validation)Affected if The theme contains dynamic file inclusion using unsanitized user input in include/require statements
-
Verify user input reaches file inclusion functionsInspect the identified inclusion code to confirm that $_GET, $_POST, or other user-supplied data directly or indirectly influences the included file path without validationAffected if User-controllable parameters (GET/POST requests) flow into file inclusion functions without sanitization or allowlist validation
-
Check PHP configuration for file inclusion settingsReview php.ini for allow_url_include=Off (should be off; on increases risk) and verify open_basedir restrictions are in place if possibleAffected if allow_url_include is enabled or no open_basedir restriction exists, increasing exploitability of LFI
-
Confirm the vulnerable file is accessibleTest if the file inclusion entry point is reachable via web requests (check routing, templates, or AJAX endpoints that accept file parameters)Affected if The vulnerable file inclusion functionality is accessible without authentication or is exposed through a web-accessible endpoint
You are affected if the Capie theme version is below 1.0.41 AND the theme contains accessible file inclusion code that uses unsanitized user input.
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 version 1.0.41 or later if available. Otherwise, implement strict input validation using allowlists, avoid using user input directly in include/require statements, and ensure PHP's allow_url_include is disabled.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31060 — 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-31060 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