dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-24770

HIGH · 8.1 CVSS v3.1 Published 2025-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in BZOTheme CraftXtore bw-craftxtore allows PHP Local File Inclusion.This issue affects CraftXtore: from n/a through <= 1.7.

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 confidence

A PHP Local File Inclusion (LFI) vulnerability exists in the CraftXtore theme where user-controlled input is used in include/require statements without proper validation, allowing attackers to read sensitive files on the server or potentially achieve remote code execution in certain configurations.

MitigationImplement strict input validation and whitelisting for file inclusion paths; use basename() and realpath() to normalize and validate included files against an allowed directory.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if CraftXtore theme is installed
    Search for theme files: look for directories named 'craftxtore' or files containing 'CraftXtore' in the web root. Common paths: /wp-content/themes/craftxtore/ (if WordPress) or /app/themes/craftxtore/.
    Affected if The CraftXtore theme directory exists in the environment
  2. Locate PHP files using include/require
    Search for PHP files in the theme directory containing 'include(' or 'require(' or 'include_once(' or 'require_once('. Use grep or file search tools.
    Affected if PHP files with inclusion functions exist in the theme
  3. Identify user input in inclusion statements
    Examine include/require statements for dynamic variables like $_GET, $_POST, $_REQUEST, or other user-controllable parameters. Look for patterns such as: include($_GET['file']), include($module), or require($path . $_REQUEST['name'])
    Affected if User-supplied parameters ($_GET, $_POST, $_REQUEST) are used directly in include or require statements without sanitization
  4. Check if vulnerable endpoints are accessible
    Identify PHP files that handle the vulnerable include logic and test if they can be reached via web requests. Use web logs or manual URL testing to confirm accessibility.
    Affected if The PHP files processing user input in include statements are accessible via HTTP requests
  5. Verify lack of input validation
    Review the code around include statements for validation functions like basename(), realpath(), whitelist checks, or path traversal prevention (e.g., strpos, preg_match for '../').
    Affected if No validation functions are present before the include/require statements, or validation can be bypassed
  6. Compare installed theme version to any available updates
    Check theme version file (style.css header, theme.json, or version.php) and compare to any newer versions available from the vendor or theme repository.
    Affected if The installed version predates the CVE patch date or is older than the latest available version

The environment is affected if CraftXtore theme is installed AND user-controlled input flows directly into include/require statements without validation, and those code paths are web-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and whitelisting for file inclusion paths; use basename() and realpath() to normalize and validate included files against an allowed directory.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24770 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24770 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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