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

CVE-2025-64359

HIGH · 7.5 CVSS v3.1 Published 2025-10-31
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 StylemixThemes Consulting consulting allows PHP Local File Inclusion.This issue affects Consulting: from n/a through < 6.7.5.

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 vulnerability exists in the StylemixThemes Consulting WordPress theme (versions before 6.7.5) due to improper control of filenames in include/require statements. Attackers could potentially read sensitive local files by manipulating file path parameters through user-controlled input.

MitigationUpdate Consulting theme to version 6.7.5 or later. If immediate update is not possible, implement web application firewall rules to block directory traversal patterns (e.g., ../../) in request parameters.

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 Consulting theme is installed
    Check the WordPress themes directory (wp-content/themes/) for the consulting theme folder. Run: ls -la /path/to/wordpress/wp-content/themes/ | grep -i consulting
    Affected if The consulting theme folder exists in the WordPress themes directory
  2. Identify the installed theme version
    Open the theme's style.css file located at wp-content/themes/consulting/style.css and locate the 'Version:' declaration in the file header comment block at the top
    Affected if The version number is present and is less than 6.7.5 (for example: 6.7.4, 6.7.3, 6.7.2, or earlier)
  3. Search for vulnerable include/require patterns
    Search the theme's PHP files for dynamic include/require statements. Run: grep -rn 'include\|require' wp-content/themes/consulting/ --include='*.php' | grep '\$_' to find includes that use request variables
    Affected if PHP files contain include or require statements that directly use superglobal variables like $_GET, $_POST, or $_REQUEST without sanitization
  4. Verify the vulnerable parameter is accessible
    Examine the identified include statements to determine if the affected parameter is passed via URL parameters or form inputs and is accessible without authentication
    Affected if The file inclusion parameter can be controlled through user-supplied input (GET/POST requests) without requiring admin privileges

The environment is affected if the Consulting theme is installed with a version lower than 6.7.5 AND the theme contains dynamic include/require statements that use user-controlled input without validation.

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

Update Consulting theme to version 6.7.5 or later. If immediate update is not possible, implement web application firewall rules to block directory traversal patterns (e.g., ../../) in request parameters.

Recommended fix Moderate confidence

Consulting version 6.7.5 or later

  1. 1. Back up your WordPress site (database and files) before performing any updates
  2. 2. Navigate to WordPress Admin > Appearance > Themes
  3. 3. Locate the Consulting theme and check for an available update
  4. 4. Update Consulting theme to version 6.7.5 or later
  5. 5. Verify the update completed successfully by checking the theme version number
  6. 6. Test critical site functionality to ensure the update did not break existing features
Caveat Review theme changelog for any backward-incompatible changes before upgrading; test in staging environment first if possible

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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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