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

CVE-2025-69395

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 Gable gable allows PHP Local File Inclusion.This issue affects Gable: from n/a through <= 1.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

The ThemeREX Gable WordPress theme (versions up to 1.5) contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly used in include/require statements without adequate validation, allowing attackers to include arbitrary local PHP files and potentially achieve remote code execution.

MitigationImplement strict input validation and whitelist-based filtering on file inclusion paths, use basename() and realpath() to sanitize user input, or replace dynamic includes with static requires. If a patched theme version exists, update immediately; otherwise, consider deploying a WAF rule as a temporary mitigation.

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 ThemeREX Gable theme is installed
    Check your WordPress installation's wp-content/themes/ directory for a folder named 'gable' or 'trx_gable'. In WordPress admin, go to Appearance > Themes to see if the theme is active or installed.
    Affected if The theme folder exists in the themes directory or appears in WordPress admin theme list.
  2. Determine the installed theme version
    Open the theme's style.css file located in wp-content/themes/gable/ (or similar path) and look for the 'Version:' header in the file comments. Alternatively, check the main theme PHP file for a version constant or variable.
    Affected if The version is 1.5 or lower, or no version is declared (indicating an unmodified installation).
  3. Locate dynamic include/require statements
    Search theme PHP files for patterns like 'include(', 'require(', 'include_once(', or 'require_once(' where variables or request parameters are used as the path. Look in files within the theme folder, particularly in template files or shortcode handlers.
    Affected if Dynamic file inclusion statements using $_GET, $_POST, or other user-controlled input are found without proper sanitization.
  4. Inspect file inclusion parameters
    Examine any PHP files that handle file path parameters. Look for code that uses parameters like 'template', 'file', 'page', 'path', or similar in $_REQUEST, $_GET, or $_POST arrays directly in include/require calls.
    Affected if User-supplied parameters are passed directly to include/require statements without validation functions like basename(), realpath(), or whitelist checks.
  5. Verify theme is actively processing file requests
    Test if the theme processes file inclusion requests by examining server logs or attempting a benign local file inclusion probe (e.g., requesting a known safe file). Check if the theme routing handles parameters that could be exploited.
    Affected if The theme accepts and processes file path parameters through HTTP requests that trigger dynamic includes.

You are affected if the ThemeREX Gable theme is installed at version 1.5 or below and contains dynamic include/require statements using unvalidated user input for file paths.

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

Implement strict input validation and whitelist-based filtering on file inclusion paths, use basename() and realpath() to sanitize user input, or replace dynamic includes with static requires. If a patched theme version exists, update immediately; otherwise, consider deploying a WAF rule as a temporary mitigation.

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-69395 — 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-69395 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