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

CVE-2025-69396

HIGH · 8.1 CVSS v3.1 Published 2026-02-20
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 ThemeREX Splendour splendour allows PHP Local File Inclusion.This issue affects Splendour: from n/a through <= 1.23.

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 ThemeREX Splendour WordPress theme contains a PHP Local File Inclusion (LFI) vulnerability caused by improper control of filenames in include/require statements. This allows attackers to potentially include and execute arbitrary PHP files from the server, leading to remote code execution.

MitigationUpdate the Splendour theme to the latest patched version immediately. If no patch is available, consider removing the theme or implementing WAF rules to block directory traversal patterns (e.g., ../../../) in URL 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
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. Identify if Splendour theme is installed
    Check the WordPress themes directory for the Splendour theme folder, typically located at wp-content/themes/splendour or wp-content/themes/splendour-theme. Look for a folder containing style.css and other theme files.
    Affected if The Splendour theme folder exists in the WordPress themes directory.
  2. Determine the installed theme version
    Open the theme's style.css file located in the Splendour theme folder and locate the version comment in the theme header (usually near the top labeled 'Version: x.x.x'). Compare this version number to any available patched versions from ThemeREX.
    Affected if The installed version is older than the latest patched version released by ThemeREX for this vulnerability.
  3. Locate potentially vulnerable include/require statements
    Search the theme's PHP files (especially in include/ or inc/ directories within the theme folder) for include(), require(), include_once(), or require_once() statements that use variables or request parameters in the file path without proper sanitization (e.g., include($_GET['file'])).
    Affected if The theme contains PHP include/require statements that accept unsanitized user input for file paths.
  4. Identify exploitable URL parameters
    Examine the theme's PHP files for parameters passed via GET or POST requests that are used in file inclusion functions. Common vulnerable patterns include parameters named 'file', 'path', 'template', 'page', 'theme', or 'slug' being used in include/require statements.
    Affected if URL parameters (especially in PHP files accessible via web) accept file paths and are used in include/require statements without validation.
  5. Test for directory traversal vulnerability
    If vulnerable parameters are identified, manually test (or review access logs for) requests containing directory traversal sequences such as ../../../wp-config.php or ../../../../etc/passwd passed to the identified parameters.
    Affected if The application allows directory traversal sequences (../) in the identified parameters and includes files from the server filesystem.

The environment is affected if the ThemeREX Splendour theme is installed, uses an unpatched version, and contains PHP include/require statements that accept unsanitized user input which can be manipulated to perform directory traversal.

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 the Splendour theme to the latest patched version immediately. If no patch is available, consider removing the theme or implementing WAF rules to block directory traversal patterns (e.g., ../../../) in URL parameters.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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