CVE-2025-54003
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 Mikado-Themes Depot depot allows PHP Local File Inclusion.This issue affects Depot: from n/a through <= 1.16.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Mikado-Themes Depot theme. The vulnerability allows attackers to include and execute arbitrary local PHP files due to improper control of filename parameters in include/require statements within the theme's code.
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.
-
Confirm Mikado-Themes Depot theme installationLocate theme files in the web root, typically under wp-content/themes/ or the theme directory structure. Look for folder names containing 'depot' or 'mikado'.Affected if The Depot theme folder is present in the themes directory.
-
Identify the installed theme versionOpen the theme's style.css file (usually in the theme root) and look for the 'Version:' comment header. Alternatively, check functions.php or theme.json for version information.Affected if The version cannot be determined from theme files or differs from the latest release.
-
Search for insecure include/require statementsGrep the theme's PHP files for include, include_once, require, or require_once statements that use variables without sanitization (e.g., include($file), include($_GET['page']). Review the context around these statements.Affected if The theme code contains include/require statements using unsanitized variable input from user sources (GET, POST, COOKIE).
-
Identify web-accessible input vectorsExamine publicly accessible PHP files (in the theme root or subdirectories) for parameters that could influence file paths. Look for query string parameters like ?file=, ?page=, ?template=, or ?path=.Affected if Web-accessible parameters can be manipulated to control which files are included.
-
Check for path traversal protectionTest whether file inclusion attempts using ../ sequences are blocked. Review code for realpath(), basename(), or whitelist validation before file inclusion operations.Affected if No path traversal protections exist, or validation can be bypassed.
A user is affected if the Mikado-Themes Depot theme is installed, contains include/require statements using unsanitized variables, and has web-accessible input points that could be manipulated for local file inclusion.
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 dataUpdate the Depot theme to the latest version immediately. If no patch is available, audit the theme code for insecure include/require statements and implement strict input validation or whitelist-based file inclusion to prevent path traversal.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54003 — 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-54003 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