CVE-2026-35449

The install/test.php diagnostic script has its CLI-only access guard disabled by commenting out the die() statement. The script remains accessible via HTTP after installation, exposing video viewer statistics including IP addresses, session IDs, and user agents to unauthenticated visitors.

Details

The disabled guard at install/test.php:5-7:

if (!isCommandLineInterface()) {
    //return die('Command Line only');
}

The script also enables verbose error reporting:

error_reporting(E_ALL);
ini_set('display_errors', '1');

It then queries VideoStatistic::getLastStatistics() and outputs the result via var_dump():

$resp = VideoStatistic::getLastStatistics(getVideos_id(), User::getId());
var_dump($resp);

The VideoStatistic object contains: ip (viewer IP address), session_id, user_agent, users_id, and JSON metadata. The display_errors=1 setting also leaks internal filesystem paths in any PHP warnings.

The install/ directory is not restricted by .htaccess (it only disables directory listing via Options -Indexes) and no web server rules block access to individual PHP files in this directory.

Proof of Concept

# Request viewer stats for video ID 1
curl "https://your-avideo-instance.com/install/test.php?videos_id=1"

Confirmed accessible on live AVideo instances (HTTP 200).

Unauthenticated disclosure of viewer IP addresses (PII under GDPR), session identifiers, and user agents. The enabled display_errors also reveals internal server paths on errors.

• CWE: CWE-200 (Exposure of Sensitive Information)
• Severity: Low

CVE-2026-35449 has a CVSS score of 5.3 (Medium). 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

Uncomment the CLI guard at install/test.php:6 to restore the intended access restriction:

if (!isCommandLineInterface()) {
    return die('Command Line only');
}

Found by aisafe.io

1. What is CVE-2026-35449? CVE-2026-35449 is a medium-severity security vulnerability in wwbn/avideo (composer), affecting versions <= 26.0. No fixed version is listed yet.
2. How severe is CVE-2026-35449? CVE-2026-35449 has a CVSS score of 5.3 (Medium). 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-35449? wwbn/avideo (composer) versions <= 26.0 is affected.
4. Is there a fix for CVE-2026-35449? No fixed version is listed for CVE-2026-35449 yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is CVE-2026-35449 exploitable, and should I be worried? Whether CVE-2026-35449 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-35449 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.