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

CVE-2025-69373

HIGH · 7.5 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 →
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 beeteam368 VidoRev vidorev allows PHP Local File Inclusion.This issue affects VidoRev: from n/a through <= 2.9.9.9.9.9.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 · high confidence

This is a PHP Local File Inclusion (LFI) vulnerability in the VidoRev WordPress theme (beeteam368). The vulnerability exists due to improper control of filenames used in PHP include/require statements, allowing attackers to manipulate file path parameters to include arbitrary files from the server. This can lead to exposure of sensitive files, source code disclosure, or potentially remote code execution if the attacker can inject malicious PHP code into accessible files.

MitigationUpgrade VidoRev to the latest version (beyond 2.9.9.9.9.7) which should contain the patched code. If no update is available, implement input validation on all file path parameters to prevent directory traversal attacks (e.g., blocking sequences like '../' and implementing allowlist-based file inclusion), and ensure all user-supplied data is sanitized before being used in include/require statements.

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 VidoRev theme installation
    Navigate to wp-content/themes/ in your WordPress installation and verify the 'vidorev' or 'beeteam368' theme directory exists
    Affected if The VidoRev theme directory is present on the server
  2. Check installed VidoRev version
    Open the theme's style.css file (usually at wp-content/themes/vidorev/style.css or wp-content/themes/beeteam368/style.css) and locate the 'Version:' header in the file header comment
    Affected if The version number is 2.9.9.9.9.7 or lower, or if no version is declared and the theme is VidoRev/beeteam368
  3. Identify vulnerable file inclusion parameters
    Search theme PHP files for patterns like 'include(', 'require(', 'include_once(', 'require_once(' where variable parameters are used, especially examining files in the theme'sinc/ or includes/ directories; look for parameters named similarly to 'file', 'path', 'slug', or 'template' that accept user input
    Affected if PHP include/require statements use unsanitized user-supplied parameters directly in the file path without validation (e.g., include($_GET['file']); or require($path . $_GET['template']);)
  4. Test for directory traversal possibility
    If vulnerable file inclusion parameters are found in the code, examine whether the code sanitizes input by checking for '../' sequences or uses basename() or realpath() functions to prevent directory traversal
    Affected if The code does not filter or block '../' sequences and allows direct use of user input in file paths, enabling attackers to traverse outside intended directories

You are affected if VidoRev theme version is 2.9.9.9.9.7 or lower AND the theme contains PHP file inclusion code that uses user-supplied parameters without sanitizing directory traversal sequences.

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 VidoRev to the latest version (beyond 2.9.9.9.9.7) which should contain the patched code. If no update is available, implement input validation on all file path parameters to prevent directory traversal attacks (e.g., blocking sequences like '../' and implementing allowlist-based file inclusion), and ensure all user-supplied data is sanitized before being used in include/require statements.

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