CVE-2025-58705
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 Axiomthemes Crafti allows PHP Local File Inclusion. This issue affects Crafti: from n/a through 1.12.
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 confidenceA Local File Inclusion (LFI) vulnerability exists in the Crafti theme by Axiomthemes due to improper control of filenames in PHP include/require statements. This allows attackers to include arbitrary local PHP files by manipulating the filename parameter, potentially leading to code execution.
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 Crafti theme installationSearch the webroot for directories or files containing 'crafti' or 'axiomthemes' branding, such as theme configuration files, style.css with Crafti/Axiomthemes metadata, or template filesAffected if The Crafti theme by Axiomthemes is present in the web application
-
Find PHP files with dynamic file inclusionSearch the theme directory for PHP files using include, require, include_once, or require_once with variable arguments (e.g., include($var);)Affected if The theme contains PHP files that dynamically construct file paths for inclusion
-
Identify user-controlled file path parametersExamine PHP files for request parameters (from $_GET, $_POST, or $_REQUEST) passed directly to include/require statements without sanitizationAffected if File inclusion functions receive input directly from user requests without validation or filtering
-
Locate the vulnerable parameterReview the identified PHP files to find the specific parameter name used in the file inclusion (e.g., 'file', 'page', 'template', 'path')Affected if A parameter exists that can be manipulated to alter the file path being included
-
Check PHP configuration for additional riskReview PHP configuration (phpinfo or php.ini) for allow_url_include settingAffected if allow_url_include is enabled, which would allow remote file inclusion in addition to local file inclusion
A system is affected if the Crafti theme is installed and contains PHP files where user-supplied parameters are used in include/require statements without proper validation, allowing path traversal to access arbitrary local files.
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 dataImplement strict input validation on all file inclusion parameters, use allowlists for permitted files, and ensure include/require statements cannot accept user-supplied paths. Consider using basename() and directory containment checks.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58705 — 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-58705 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