CVE-2025-25172
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in beeteam368 VidMov vidmov allows PHP Local File Inclusion.This issue affects VidMov: from n/a through <= 1.9.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 confidenceThe VidMov theme for WordPress contains a Local File Inclusion (LFI) vulnerability allowing attackers to include arbitrary PHP files from the server. This occurs due to improper control of filenames in include/require statements, potentially enabling remote code execution when attackers can control which files are included.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm VidMov theme is installedNavigate to wp-content/themes/ directory and check for a folder named 'vidmov' or similar. In WordPress admin, go to Appearance > Themes to verify VidMov is active.Affected if VidMov theme is present in the WordPress installation
-
Identify the installed VidMov versionCheck the theme's style.css file in the theme directory for the 'Version:' header, or look for a version.php/changelog file within the theme folder.Affected if The installed version matches or falls within an affected version range (compare to any published vulnerable versions)
-
Locate file inclusion functions in theme codeSearch theme PHP files for patterns like 'include(', 'require(', 'include_once(', 'require_once(' where variables or request parameters are used directly in the path (e.g., include $_GET['file']).Affected if Any include/require statements accept user input (GET/POST parameters) without sanitization
-
Audit WordPress access logs for suspicious file inclusion requestsReview server access logs (Apache/nginx) for requests to PHP files with unusual query parameters that might indicate LFI probing (e.g., ?file=../../wp-config.php).Affected if Logs show requests with path traversal patterns or direct file inclusion attempts targeting the VidMov theme
-
Verify input validation on file inclusion parametersIf the theme uses any parameters for file inclusion, trace the code flow to confirm they are validated against an allowlist or sanitized before use in include/require statements.Affected if No validation exists or user-controlled input flows directly to file inclusion functions
A user is affected if VidMov theme is installed and contains unsafe file inclusion code that allows user-controlled input to control which files are included.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate VidMov to the latest patched version. If no patch is available, implement strict input validation on all file inclusion parameters, disable allow_url_fopen/allow_url_include, and review code for unsafe use of include/require with user-controlled input.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25172 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-25172 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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