CVE-2026-35449
Information Disclosure via Accessible install/test.php in WWBN AVideo
Publication date: 2026-04-06
Last updated on: 2026-04-23
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wwbn | avideo | to 26.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-200 | The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in WWBN AVideo versions 26.0 and prior, where the install/test.php diagnostic script's CLI-only access guard is disabled by commenting out the die() statement.
As a result, the script remains accessible via HTTP after installation, allowing unauthenticated visitors to access it.
This exposure reveals video viewer statistics such as IP addresses, session IDs, and user agents.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the install/test.php diagnostic script is accessible via HTTP on your WWBN AVideo installation. Since the CLI-only access guard is disabled, the script remains accessible after installation.
You can use commands like curl or wget to test access to the script endpoint. For example:
- curl -I http://your-avideo-domain/install/test.php
- wget --spider http://your-avideo-domain/install/test.php
If the HTTP response status is 200 OK and the content reveals video viewer statistics including IP addresses, session IDs, or user agents without authentication, the vulnerability is present.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, you should restrict or remove access to the install/test.php diagnostic script after installation.
Specifically, re-enable the CLI-only access guard by uncommenting the die() statement in the install/test.php script to prevent HTTP access.
Alternatively, you can remove or rename the install/test.php file to prevent unauthenticated access to sensitive video viewer statistics.
Additionally, consider implementing web server access controls (e.g., .htaccess rules or firewall rules) to block external HTTP requests to this script.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive information including IP addresses, session IDs, and user agents of video viewers.
Such exposure could be exploited to track users, hijack sessions, or gather intelligence about user behavior without consent.
However, the vulnerability does not impact integrity or availability of the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability exposes video viewer statistics including IP addresses, session IDs, and user agents to unauthenticated visitors. Such exposure of personal and session data could potentially lead to non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal information and ensuring that unauthorized parties cannot access sensitive user data.
Specifically, GDPR mandates protection of personal data such as IP addresses, and unauthorized disclosure could violate principles of data confidentiality and security. Similarly, HIPAA requires protection of any identifiable health information, and while this vulnerability may not directly expose health data, the exposure of session and user information could still pose compliance risks depending on the context of use.