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

CVE-2025-62753

HIGH · 7.5 CVSS v3.1 Published 2025-12-30
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 MadrasThemes MAS Videos masvideos allows PHP Local File Inclusion.This issue affects MAS Videos: from n/a through <= 1.3.4.

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

MAS Videos WordPress plugin versions 1.3.4 and below contain a Local File Inclusion (LFI) vulnerability where the application improperly validates filenames used in PHP include/require statements. This allows unauthenticated attackers to include arbitrary local PHP files, potentially leading to remote code execution if they can control the included files or leverage path traversal sequences.

MitigationUpdate MAS Videos to the latest available version. If no patched version exists, disable the plugin and implement WAF rules blocking directory traversal patterns (../) to mitigate exploitation until a fix is released.

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 MAS Videos plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate MAS Videos. Note the version number displayed. Alternatively, check the plugin directory: wp-content/plugins/mas-videos/ and locate the main plugin file (usually mas-videos.php) to read the Version header.
    Affected if MAS Videos plugin is installed and the version is 1.3.4 or lower
  2. Confirm the plugin is active
    In WordPress admin, verify that MAS Videos shows as 'Active' in the Plugins list. An inactive plugin cannot be exploited by unauthenticated attackers.
    Affected if MAS Videos plugin is currently active on the WordPress site
  3. Locate the vulnerable include/require code
    Search the mas-videos plugin directory for PHP include, include_once, require, or require_once statements that use variables in the file path (e.g., include($file), require($_GET['file']). Look in files within the plugin structure, particularly any file handling or template-related files.
    Affected if The plugin contains include/require statements that dynamically use user-controlled input without proper validation
  4. Identify the vulnerable parameter
    Examine the include/require statements found and trace back what variables are used. Check if any HTTP request parameter (GET/POST) directly or indirectly feeds into these include statements.
    Affected if A user-accessible parameter (via GET or POST request) can influence the filename in the include/require statement
  5. Test for path traversal capability
    If a vulnerable parameter exists, attempt to use ../ sequences in the parameter value (e.g., ../../wp-config.php) to see if the application allows traversal outside the intended directory. This should be done in a non-production environment only.
    Affected if The application permits directory traversal characters (.., ../) in the vulnerable parameter, allowing inclusion of files outside the intended directory

You are affected if MAS Videos plugin version 1.3.4 or lower is installed and active, and the plugin contains include/require statements that allow user-controlled input to specify filenames with path traversal capability.

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

Update MAS Videos to the latest available version. If no patched version exists, disable the plugin and implement WAF rules blocking directory traversal patterns (../) to mitigate exploitation until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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