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

CVE-2025-64205

HIGH · 8.1 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 →
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 TieLabs Jannah jannah allows PHP Local File Inclusion.This issue affects Jannah: from n/a through <= 7.6.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 · moderate confidence

The TieLabs Jannah WordPress theme through version 7.6.0 contains a PHP Local File Inclusion (LFI) vulnerability. Attackers can manipulate file path parameters in include/require statements to read sensitive local files on the server, potentially exposing configuration files, credentials, or other sensitive data.

MitigationUpdate to a patched version of Jannah if available. Otherwise, implement strict input validation on all file inclusion parameters and consider deploying a WAF rule to block directory traversal patterns as a temporary control.

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. Locate Jannah theme installation
    In your WordPress installation, navigate to wp-content/themes/ and verify the presence of a folder named 'jannah' or 'jannah-theme'. List the contents to confirm theme files are installed.
    Affected if The jannah theme directory exists in the WordPress themes folder
  2. Determine installed Jannah version
    Open the style.css file within the jannah theme directory and locate the 'Version:' declaration in the CSS header comment. Alternatively, check version constants in functions.php.
    Affected if The version is 7.6.0 or lower (any version up to and including 7.6.0)
  3. Identify unsafe file inclusion patterns
    Search all PHP files in the theme for include, include_once, require, or require_once statements that concatenate or interpolate user input into file paths (e.g., include($_GET['file']). Use grep or a code editor to find patterns like 'include($', 'require($', or similar constructs.
    Affected if PHP files contain file inclusion functions using unsanitized variables derived from request parameters
  4. Inspect for directory traversal vulnerability
    Review the identified file inclusion code paths to determine if parameters accept relative path traversal sequences such as ../ or ..\. Test whether the code filters or blocks these sequences before passing to include/require.
    Affected if The vulnerable code accepts path parameters without filtering directory traversal sequences
  5. Verify vulnerable parameter is accessible
    If the theme exposes file inclusion parameters via GET or POST requests (common in WordPress admin or AJAX endpoints), confirm these endpoints are reachable and the parameter names match those used in the unsafe include statements.
    Affected if The file inclusion parameter is exposed via HTTP request and reachable without authentication or with standard WordPress user privileges

You are affected if the Jannah theme is installed with version 7.6.0 or lower and contains PHP files with unsafe include/require statements that accept user-controlled path parameters without proper 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of Jannah if available. Otherwise, implement strict input validation on all file inclusion parameters and consider deploying a WAF rule to block directory traversal patterns as a temporary control.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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