Path TraversalWeakness · CWE-22

CVE-2025-26753

HIGH · 7.5 CVSS v3.1 Published 2025-02-25

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Improper 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

dbcve analysis · moderate confidence

A path traversal vulnerability exists in the videowhisper-live-streaming-integration plugin's Broadcast Live Video component, allowing attackers to access files outside the web root directory through specially crafted directory traversal sequences in file path parameters. This vulnerability affects versions up to and including 6.2.

MitigationImplement strict input validation and canonicalization of file paths, ensuring all path inputs are validated against an allowlist and restricted to the intended directory. Use realpath() in PHP to resolve symbolic links and verify the final resolved path stays within allowed boundaries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Locate the VideoWhisper Live Streaming Integration plugin

Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'videowhisper-live-streaming-integration' or similar. If using a Linux system, you can run: find /var/www -type d -name '*videowhisper*' 2>/dev/null

Affected if The plugin directory exists on the server
Determine the installed plugin version

Open the main plugin file (usually videowhisper-live-streaming-integration.php) and look for a version comment or header. Common paths: wp-content/plugins/videowhisper-live-streaming-integration/videowhisper-live-streaming-integration.php. Search for lines containing 'Version:' or 'Version Number:'

Affected if The version read from the plugin header is 6.2 or lower
Verify the Broadcast Live Video component exists

Look for files related to Broadcast Live Video functionality. Common locations: wp-content/plugins/videowhisper-live-streaming-integration/ or subdirectories containing 'broadcast', 'live', or 'video' in names. Check for PHP files that handle live video streaming or broadcasting. Run: find /path/to/plugin -type f -name '*.php' | xargs grep -l -i 'broadcast.*live' 2>/dev/null

Affected if The Broadcast Live Video PHP component is present and accessible via the web
Test for vulnerable path traversal parameter

Inspect the Broadcast Live Video PHP files for parameters that accept file paths. Look for common path traversal indicators: $_GET, $_POST, or $_REQUEST usage with file path variables. Search for patterns like '$_GET["file"]', '$_GET["path"]', or similar where user input might be used in file operations (file_get_contents, include, require, fopen). Check if the code lacks proper path validation (no realpath() or basename() checks)

Affected if The component accepts file path parameters without sanitization using realpath() or allowlist validation

A user is affected if the videowhisper-live-streaming-integration plugin version is 6.2 or lower and the Broadcast Live Video component is installed and accessible with path parameters that lack proper path traversal validation.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Implement strict input validation and canonicalization of file paths, ensuring all path inputs are validated against an allowlist and restricted to the intended directory. Use realpath() in PHP to resolve symbolic links and verify the final resolved path stays within allowed boundaries.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing4.0 h
Review / QA2.0 h

15.0 hours of engineering $2,640

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

patchstack.com
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26753 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-26753?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.6%

Remediation

A high-priority fix

Have this fixed 15 hrs · Moderate

Typical engagement from $2,640

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-26753 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References