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

CVE-2025-63076

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 Elements dt-the7-core allows PHP Local File Inclusion.This issue affects The7 Elements: from n/a through <= 2.7.11.

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

A PHP Local File Inclusion vulnerability in Dream-Theme The7 Elements dt-the7-core plugin allows attackers to control which PHP files get included through unsafe use of include/require statements. This can enable arbitrary code execution by including malicious local PHP files.

MitigationUpdate to a patched version of The7 Elements. If no patch is available, implement strict input validation on file inclusion parameters to restrict included files to an allowed whitelist.

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. Locate the dt-the7-core plugin installation
    Check your WordPress plugins directory at /wp-content/plugins/dt-the7-core/ or look for the plugin in your wp-admin Plugins section
    Affected if The plugin is installed and active on the WordPress site
  2. Identify the installed plugin version
    Open the main plugin file (typically dt-the7-core.php or index.php) in the plugin directory and locate the version definition in the file header comment
    Affected if The installed version has not been patched by the vendor (compare against the version noted in the CVE advisory as the fixed release)
  3. Verify the vulnerable file inclusion code exists
    Search the plugin directory for PHP files containing include or require statements that use variables without sanitization, particularly looking for patterns like 'include($variable)' or 'require($_GET'
    Affected if Unsafe include/require patterns are found that allow user-controlled input to determine which file is loaded
  4. Confirm the vulnerable parameter is accessible
    Test if the plugin exposes any front-end or admin AJAX endpoints that accept file path parameters and pass them to unsafe include/require calls
    Affected if The vulnerable file inclusion functionality is reachable via HTTP requests without authentication restrictions

The environment is affected if the dt-the7-core plugin is active and running an unpatched version where user-supplied input can be used to control which PHP files are included via unsafe include/require statements.

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

Update to a patched version of The7 Elements. If no patch is available, implement strict input validation on file inclusion parameters to restrict included files to an allowed whitelist.

Recommended fix Moderate confidence

Latest version of The7 Elements (dt-the7-core) after 2.7.11 - update to the most recent release available in the WordPress plugin repository

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Check the WordPress admin dashboard for plugin updates under Plugins > All Plugins.
  3. 3. Update the The7 Elements plugin (dt-the7-core) to the latest available version.
  4. 4. Verify the update was successful by confirming the new version number in the plugins list.
  5. 5. Test that the website functionality remains intact after the update.
Caveat Review changelog for any breaking changes between 2.7.11 and the new version; test in staging if possible

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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