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

CVE-2025-63074

HIGH · 7.5 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 Dream-Theme The7 dt-the7 allows PHP Local File Inclusion.This issue affects The7: from n/a through < 12.8.1.1.

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

PHP Local File Inclusion (LFI) vulnerability in Dream-Theme The7 where improper validation of filenames in include/require statements allows attackers to include arbitrary local PHP files. This can lead to code execution if the attacker can control or inject paths to malicious files.

MitigationUpgrade The7 theme to version 12.8.1.1 or later. If immediate upgrade is not possible, disable the theme and review all include/require statements for proper input validation using whitelist approaches.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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 The7 theme is installed
    Locate the theme directory - typically in wp-content/themes/the7/ or similar path under the WordPress root. Check for the presence of the7 folder and its main files like style.css, functions.php.
    Affected if The The7 theme directory exists in the WordPress themes folder.
  2. Determine The7 theme version
    Open the style.css file in the theme directory and look for the 'Version:' comment header at the top, or check functions.php for a version constant definition.
    Affected if The version listed is below 12.8.1.1 (for example, 12.8.0, 12.7.x, or earlier).
  3. Search for vulnerable include/require patterns
    In the theme directory, search for include(), require(), include_once(), or require_once() statements that accept variables in their path arguments without sanitization. Focus on files in directories like inc/, includes/, or files handling template parts.
    Affected if Dynamic include/require statements using variables (e.g., include($file); or require($_GET['page']);) are found without proper validation or whitelist checks.
  4. Verify input sources reaching include/require
    Trace how user-supplied parameters (GET, POST, COOKIE, or REQUEST) flow into the include/require paths identified in step 3. Check if parameters like 'page', 'template', 'file', or 'path' are used.
    Affected if User-controlled input directly or indirectly reaches the vulnerable include/require statements without validation.

You are affected if The7 theme version is below 12.8.1.1 AND your installation contains dynamic include/require statements that accept user input without 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade The7 theme to version 12.8.1.1 or later. If immediate upgrade is not possible, disable the theme and review all include/require statements for proper input validation using whitelist approaches.

Recommended fix High confidence

The7 version 12.8.1.1 or latest stable release

  1. 1. Create a complete backup of your WordPress site (database and files)
  2. 2. Update The7 theme to version 12.8.1.1 or the latest available version via WordPress admin dashboard (Appearance > Themes) or via the theme vendor
  3. 3. Verify the update was successful by checking the theme version in Appearance > Themes
  4. 4. Test critical site functionality to ensure the update did not break any features
  5. 5. Monitor the site for any errors or unusual behavior
Caveat Review theme documentation for any required PHP version or WordPress version changes; test in staging environment first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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