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

CVE-2025-64363

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 SeventhQueen Kleo kleo allows PHP Local File Inclusion.This issue affects Kleo: from n/a through < 5.5.0.

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 · high confidence

A PHP Local File Inclusion (LFI) vulnerability in the SeventhQueen Kleo WordPress theme allows attackers to read sensitive files on the server via manipulated file paths in include/require statements. This stems from improper control of filenames used in PHP include/require functions, enabling path traversal attacks.

MitigationUpgrade to Kleo version 5.5.0 or later to obtain the vendor patch. If immediate upgrading is not possible, deploy a WAF rule to block path traversal patterns in query parameters and review the theme's PHP files for unsanitized include/require usage.

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 Kleo theme is installed
    In WordPress admin dashboard, go to Appearance > Themes and check if the Kleo theme is active. Alternatively, check the theme directory at wp-content/themes/kleo/ and look for style.css which contains the theme version in its header comment.
    Affected if Kleo theme is active and present in the WordPress installation
  2. Identify the installed Kleo version
    Open wp-content/themes/kleo/style.css and locate the 'Version:' field in the theme header comment at the top of the file. Note the exact version number.
    Affected if The version is lower than 5.5.0 (e.g., 5.4.x, 5.3.x, or earlier)
  3. Inspect theme PHP files for vulnerable include/require patterns
    Search the theme directory (wp-content/themes/kleo/) for PHP files containing include, require, include_once, or require_once statements that use variables without sanitization. Look for patterns like 'include($_GET[...])' or 'require($variable)' in files within subdirectories.
    Affected if Unsanitized include/require statements using request variables or user-controlled input are found in theme files
  4. Check for path traversal vulnerability exposure
    If vulnerable code exists, test by attempting to access a known file via path traversal (e.g., ../../../../wp-config.php) through any plugin or theme parameter that accepts file paths. Use a safe read-only test with proper authorization only in a non-production environment.
    Affected if The application returns the contents of files outside the theme directory, confirming LFI is exploitable

A user is affected if the Kleo theme version is below 5.5.0 AND the theme contains unsanitized include/require statements that allow path traversal to read arbitrary files.

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 to Kleo version 5.5.0 or later to obtain the vendor patch. If immediate upgrading is not possible, deploy a WAF rule to block path traversal patterns in query parameters and review the theme's PHP files for unsanitized include/require usage.

Recommended fix Moderate confidence

Kleo theme version 5.5.0 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. If an update is available for Kleo theme, click Update Now
  4. Alternatively, download Kleo theme version 5.5.0 or later from the vendor (ThemeForest or SeventhQueen directly)
  5. Upload and activate the updated theme version
  6. Verify the theme is now running version 5.5.0 or higher under Appearance > Themes > Kleo > Theme Details
Caveat Review theme settings and child theme customizations after upgrade as minor visual/functional changes may occur in new versions

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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