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

CVE-2025-69399

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

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 Cobble theme (version <=1.7) contains a PHP Local File Inclusion (LFI) vulnerability where the application improperly controls filenames used in include/require statements. This allows attackers to include arbitrary local PHP files, potentially leading to remote code execution if they can control the included files or upload malicious content to locations the PHP process can access.

MitigationUpgrade ThemeREX Cobble to the latest version that addresses this vulnerability, or implement strict input validation and whitelisting for any user-controlled parameters used in include/require statements to prevent arbitrary file inclusion.

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 Cobble theme is installed
    Locate theme files by searching for 'cobble' or 'trx_cobble' in the wp-content/themes directory (for WordPress) or theme folder structure. Common paths: /wp-content/themes/cobble/ or /themes/cobble/
    Affected if The theme folder named 'cobble' or containing 'cobble' branding is present on the server
  2. Determine the installed theme version
    Open the theme's style.css, info.txt, or theme.json file and locate the 'Version:' header, or check version.php if it exists. Compare the version number against the affected range <=1.7
    Affected if The reported version is 1.7 or any lower version number
  3. Locate include/require statements in theme PHP files
    Search all PHP files in the theme directory for patterns like 'include(', 'require(', 'include_once(', 'require_once(' where a variable is used directly, such as 'include($', 'require($_', 'include(${$'. Use grep or a code search tool across the theme folder
    Affected if PHP files contain include/require statements that use variable parameters without sanitization (e.g., include($_GET['file']); or include($file); where $file originates from user input)
  4. Identify parameters that flow from user input to include/require
    Review the vulnerable include/require code found in step 3. Trace the variable back to its source (GET, POST, COOKIE, REQUEST parameters). Check if the parameter is used directly or with minimal string concatenation in the include/require call
    Affected if User-supplied parameters (from URL, form, or cookie) are passed directly or with minimal manipulation into include or require statements
  5. Check for unexpected files in accessible directories
    Inspect directories that the PHP process can read: wp-content/uploads/, /tmp/, /var/tmp/, or any writable folder. Look for unfamiliar .php files, suspicious .txt files, or files with encoded content that may have been uploaded as part of an LFI exploitation
    Affected if Unexpected PHP files exist in upload folders or temporary directories, or existing files have been modified with malicious code
  6. Review access logs for LFI exploitation patterns
    Examine web server access logs (access.log, error.log) for requests containing path traversal sequences like '../', '..\', or absolute paths in query parameters that match theme include endpoints. Search for patterns such as '?file=', '?page=', '?template=' with directory traversal characters
    Affected if Logs show requests with ../ sequences or absolute file paths targeting theme PHP files, indicating scanning or exploitation attempts

You are affected if the ThemeREX Cobble theme version is 1.7 or lower AND the theme's PHP code uses include/require statements with unsanitized user-controlled parameters.

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

Upgrade ThemeREX Cobble to the latest version that addresses this vulnerability, or implement strict input validation and whitelisting for any user-controlled parameters used in include/require statements to prevent arbitrary file inclusion.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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