Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-33238: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in WWBN AVideo

0
Medium
VulnerabilityCVE-2026-33238cvecve-2026-33238cwe-22
Published: Fri Mar 20 2026 (03/20/2026, 23:31:35 UTC)
Source: CVE Database V5
Vendor/Project: WWBN
Product: AVideo

Description

WWBN AVideo is an open source video platform. Prior to version 26.0, the `listFiles.json.php` endpoint accepts a `path` POST parameter and passes it directly to `glob()` without restricting the path to an allowed base directory. An authenticated uploader can traverse the entire server filesystem by supplying arbitrary absolute paths, enumerating `.mp4` filenames and their full absolute filesystem paths wherever they exist on the server — including locations outside the web root, such as private or premium media directories. Version 26.0 contains a patch for the issue.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/20/2026, 23:39:04 UTC

Technical Analysis

CVE-2026-33238 is a path traversal vulnerability classified under CWE-22 affecting WWBN AVideo, an open-source video platform. The vulnerability exists in versions prior to 26.0 within the listFiles.json.php endpoint, which accepts a POST parameter named 'path'. This parameter is passed directly to the PHP glob() function without any validation or restriction to a designated base directory. As a result, an authenticated user with uploader privileges can supply arbitrary absolute paths to traverse the server’s filesystem beyond the intended media directories. This enables the attacker to enumerate all .mp4 files on the server, including those stored outside the web root, such as private or premium content directories. The vulnerability does not allow file modification or deletion but exposes sensitive information about file locations and media assets, which could facilitate further attacks or unauthorized access. The flaw requires authentication but no additional user interaction, and the attack surface is limited to authenticated uploaders. The issue was addressed in version 26.0 by implementing proper path restrictions to confine file enumeration to allowed directories. No known exploits are currently reported in the wild. The CVSS v3.1 base score is 4.3, reflecting a medium severity with network attack vector, low attack complexity, and limited confidentiality impact.

Potential Impact

The primary impact of this vulnerability is unauthorized information disclosure. By enumerating .mp4 files and their absolute paths, an attacker can gain insights into the server’s directory structure and media assets, including private or premium content that should not be publicly accessible. This could lead to privacy violations, intellectual property theft, or facilitate targeted attacks such as social engineering or privilege escalation. While the vulnerability does not allow direct modification or deletion of files, the disclosed information could be leveraged in multi-stage attacks. Organizations hosting sensitive or proprietary video content on affected versions of WWBN AVideo are at risk of exposing valuable media assets. The requirement for authentication limits the attack to users with uploader privileges, reducing the scope but still posing a significant risk if credentials are compromised or insider threats exist. The vulnerability could undermine customer trust and lead to regulatory compliance issues if sensitive content is exposed.

Mitigation Recommendations

The most effective mitigation is to upgrade WWBN AVideo to version 26.0 or later, where the vulnerability is patched by restricting the 'path' parameter to an allowed base directory. Until upgrading is possible, organizations should implement strict access controls on uploader accounts to minimize the risk of credential compromise. Additionally, web application firewalls (WAFs) can be configured to detect and block suspicious path traversal patterns in POST requests to listFiles.json.php. Logging and monitoring of file enumeration activities by authenticated users should be enhanced to detect anomalous behavior. Code-level mitigations include sanitizing and validating the 'path' parameter to ensure it cannot reference directories outside the intended media folders. Restricting filesystem permissions to prevent the web server user from accessing sensitive directories can also reduce impact. Regular security audits and penetration testing should verify that no other endpoints expose similar path traversal flaws.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-18T02:42:27.508Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69bdda56b462d409683a8be3

Added to database: 3/20/2026, 11:37:58 PM

Last enriched: 3/20/2026, 11:39:04 PM

Last updated: 3/21/2026, 3:53:27 AM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses