CVE-2025-26752
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in videowhisper Broadcast Live Video videowhisper-live-streaming-integration allows Path Traversal.This issue affects Broadcast Live Video: from n/a through <= 6.2.
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 confidencePath traversal vulnerability in videowhisper Broadcast Live Video plugin (versions <= 6.2) allows attackers to access files outside the restricted directory through manipulated file path inputs in the plugin's file handling functionality.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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.
-
Verify the plugin is installedCheck your WordPress installation for the videowhisper-live-streaming-integration plugin in wp-content/plugins/ or via the WordPress admin Plugins pageAffected if The plugin is present in the plugins directory or listed in the WordPress admin
-
Determine the installed plugin versionRead the main plugin file header (usually videowhisper-live-streaming-integration.php) to find the Version comment, or check via WordPress admin Plugins > Installed PluginsAffected if The version is 6.2 or lower (the affected range per the CVE)
-
Confirm the Broadcast Live Video component is activeCheck if the Broadcast Live Video functionality is enabled in the plugin settings or is accessible via the WordPress frontend/admin interfaceAffected if The Broadcast Live Video component is enabled and accessible to users
-
Identify if the file handling functionality is exposedLocate the plugin code handling file paths in the Broadcast Live Video component; look for file include/require statements or file access functions that accept user inputAffected if The component processes file paths without proper validation (path traversal is possible)
-
Review access logs for suspicious patternsCheck web server access logs for requests to the plugin endpoint containing ../ patterns or unusual file pathsAffected if Such requests have been made to the affected component
You are affected if the videowhisper-live-streaming-integration plugin versions 6.2 or lower are installed AND the Broadcast Live Video component is active and accessible.
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 dataUpgrade to a patched version if available; otherwise, implement strict input validation and path sanitization to ensure all file paths resolve within the intended directory and block traversal sequences (.. , /) in user-supplied paths.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26752 — 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-26752 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