CVE-2025-58707
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 Spin allows PHP Local File Inclusion. This issue affects Spin: from n/a through 1.8.
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 confidenceThe Axiomthemes Spin theme (versions through 1.8) contains a PHP Local File Inclusion (LFI) vulnerability where the application improperly controls filenames used in include/require statements. Attackers can manipulate file path parameters to include arbitrary PHP files from the server, potentially achieving remote 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 Spin theme installationLocate the Spin theme directory in the WordPress/WooCommerce themes folder, typically at wp-content/themes/spin/ or similar path. Check for the existence of style.css with Theme Name: Spin by AxiomthemesAffected if The Spin theme by Axiomthemes is not installed in the environment
-
Identify PHP files with include/require statementsSearch the theme directory for PHP files containing include, include_once, require, or require_once statements. Use grep or similar: grep -r "include(\|require(\|include_once(\|require_once(" path/to/theme/Affected if No PHP files with inclusion statements are found in the theme
-
Detect user input in inclusion pathsExamine PHP files for patterns where $_GET, $_POST, $_REQUEST, or similar superglobals are used directly as the path parameter in include/require statements without sanitization. Look for patterns like: include($_GET['file']); or require($_REQUEST['page']);Affected if User-supplied input is used directly in include/require without basename() or allowlist validation
-
Verify absence of input validationReview the identified vulnerable inclusion code to confirm there is no basename(), pathinfo(), or allowlist validation before the include/require statement. Check that the code does not restrict file paths to a predefined listAffected if The file inclusion code lacks basename() or allowlist validation on the user input parameter
-
Check for exposed vulnerable parametersIf the vulnerable code uses $_GET or $_REQUEST parameters, verify these are accessible via URL query strings. Test by examining the application's routing to confirm the parameter can be controlled by external requestsAffected if The vulnerable parameter can be controlled through external HTTP requests
A system is affected if the Axiomthemes Spin theme is installed and contains PHP code that uses user-supplied input directly in include/require statements without basename() or allowlist validation.
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 using basename() and realpath() to ensure only allowed files can be included; disable allow_url_include in php.ini; consider using a whitelist approach for permitted include files.
- 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-58707 — 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-58707 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