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

CVE-2025-64193

HIGH · 7.5 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 8theme XStore xstore allows PHP Local File Inclusion.This issue affects XStore: from n/a through < 9.6.1.

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

Local File Inclusion vulnerability in the XStore WordPress theme allows attackers to include arbitrary PHP files from the server file system via improper control of filename parameters in include/require statements, potentially leading to remote code execution.

MitigationUpgrade XStore theme to version 9.6.1 or later. If immediate patching is not feasible, disable the theme or implement web application firewall rules to block suspicious file inclusion requests.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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. Confirm XStore theme is installed
    Navigate to wp-content/themes/ directory or check via WordPress admin dashboard under Appearance > Themes to verify the XStore theme is present.
    Affected if XStore theme is active or installed on the WordPress site.
  2. Identify installed XStore theme version
    Open the style.css file in wp-content/themes/xstore/ and locate the 'Version:' header in the theme comments, or check the version displayed in the WordPress admin theme details panel.
    Affected if Unable to determine the version or version is below 9.6.1.
  3. Compare version against vulnerable range
    Compare the identified version number to the fixed version 9.6.1. Versions below 9.6.1 are affected by this Local File Inclusion vulnerability.
    Affected if Installed version is below 9.6.1.
  4. Review access logs for file inclusion patterns
    Examine web server access logs (Apache error.log, Nginx access.log) for suspicious requests containing ../ paths or direct references to PHP files in the theme directory, such as patterns like ?file=../../ or include/require statements with user-controlled parameters.
    Affected if Logs show anomalous file inclusion requests targeting theme files.
  5. Check for unauthorized PHP files in theme directory
    List all PHP files in wp-content/themes/xstore/ and compare against the original theme package. Look for unfamiliar PHP files or recently modified files that may indicate exploitation attempts.
    Affected if Unexpected PHP files exist or known theme files have been recently modified.

The environment is affected if the XStore WordPress theme is installed with a version prior to 9.6.1, as these versions contain the vulnerable include/require code paths susceptible to Local File Inclusion.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade XStore theme to version 9.6.1 or later. If immediate patching is not feasible, disable the theme or implement web application firewall rules to block suspicious file inclusion requests.

Recommended fix High confidence

9.6.1 or later

  1. Backup your WordPress site (database and files) before proceeding with any updates
  2. Download XStore theme version 9.6.1 or later from the official 8theme marketplace or WordPress theme repository
  3. Update the XStore theme through WordPress Admin > Appearance > Themes, or via FTP/SFTP by replacing the theme files
  4. Verify the theme update was successful by checking the theme version in WordPress Admin > Appearance > Themes
  5. Clear any caching mechanisms (site cache, CDN cache, server-side cache) after the update
  6. Test critical site functionality to ensure the update did not introduce regressions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64193 — 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-64193 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