CVE-2025-58913
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 CactusThemes VideoPro videopro allows PHP Local File Inclusion.This issue affects VideoPro: from n/a through <= 2.3.8.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 · high confidenceCactusThemes VideoPro WordPress theme versions <= 2.3.8.1 contain a PHP Local File Inclusion (LFI) vulnerability where the application improperly validates file paths in include/require statements, allowing attackers to include arbitrary PHP files from the local filesystem.
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.
-
Locate VideoPro theme installationInspect the WordPress themes directory at wp-content/themes/ for a folder named 'videopro' or similar naming pattern from CactusThemesAffected if The videopro theme directory exists in the WordPress installation
-
Check installed VideoPro versionOpen the theme's style.css file (typically at wp-content/themes/videopro/style.css) and locate the 'Version:' header in the CSS comment block at the topAffected if The version listed is 2.3.8.1 or lower
-
Identify vulnerable include/require patternsSearch theme PHP files for include, include_once, require, or require_once statements that use variable or user-controllable path parameters (e.g., include($file), require($_GET['path']))Affected if Any include/require statements accept unsanitized variables or request parameters as file paths
-
Verify theme is activeIn WordPress admin dashboard, go to Appearance > Themes and check if VideoPro is the currently active themeAffected if VideoPro theme is enabled and serving pages on the site
-
Check for LFI indicators in HTTP parametersReview application logs or manually test by passing paths like ../../../../etc/passwd in URL parameters that the theme processes (common parameters include 'file', 'path', 'template', 'page', 'include')Affected if The application returns file contents from outside the intended theme directory
You are affected if VideoPro theme version 2.3.8.1 or lower is installed AND the theme contains include/require statements that accept unsanitized path parameters AND the theme is active on the WordPress site.
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 VideoPro theme to the latest patched version if available; otherwise, audit and harden all include/require statements with proper path validation and disable the theme until a fix is available.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58913 — 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-58913 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