CVE-2026-25464
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 · uneditedImproper 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.4.
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 confidenceLocal File Inclusion vulnerability in the TieLabs Jannah WordPress theme allows attackers to manipulate PHP include/require statements to read arbitrary files from the server filesystem. The theme <= 7.6.4 fails to properly validate or sanitize file paths used in include statements, enabling unauthenticated attackers to potentially access sensitive system files.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Jannah theme installationNavigate to WordPress admin dashboard under Appearance > Themes, or inspect wp-content/themes directory for the jannah theme folderAffected if The Jannah theme by TieLabs is present in the WordPress installation
-
Check installed theme versionOpen the style.css file within the jannah theme folder (wp-content/themes/jannah/style.css) and locate the 'Version:' header in the file comments, or check theme version via WordPress admin theme detailsAffected if The reported version is 7.6.4 or lower
-
Identify vulnerable include/require patternsSearch theme PHP files (particularly in functions.php, header.php, or any file handling template includes) for include(), require(), include_once(), or require_once() statements that use unsanitized variables from request parameters (e.g., $_GET, $_POST)Affected if Theme code contains include/require statements using raw user input without validation
-
Test for LFI exposure via HTTP parametersIf the vulnerable code uses a parameter (commonly 'template', 'file', 'path', or similar), attempt a benign test request with a known safe file path (e.g., ../../wp-config.php) to see if content is returned; alternatively, review access logs for directory traversal patternsAffected if HTTP requests with traversal patterns (../) in query parameters return file contents or succeed without error
-
Check for recent unauthorized accessReview web server access logs and WordPress audit logs for suspicious requests containing '../' or absolute file paths (e.g., /etc/passwd, wp-config.php) targeting Jannah theme endpointsAffected if Logs show directory traversal attempts or successful retrieval of sensitive files
A user is affected if the Jannah theme version is 7.6.4 or lower and the theme contains include/require logic that processes user-supplied file paths without sanitization.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Jannah theme to the latest patched version available from TieLabs. If immediate update is not feasible, disable the theme or implement web application firewall rules to block directory traversal patterns in request parameters.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25464 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25464 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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