CVE-2026-34733
Operator Precedence Bug in WWBN AVideo Script Enables Unauthorized File Deletion
Publication date: 2026-03-31
Last updated on: 2026-04-01
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-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized HTTP access to a script that can delete files from the server's temporary directory and disclose its contents. This unauthorized data exposure and potential data loss could lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and ensuring data integrity.
Specifically, the disclosure of temporary directory contents may expose sensitive information, violating confidentiality requirements. The ability to delete files without proper authorization could impact data availability and integrity, further risking compliance breaches.
Can you explain this vulnerability to me?
This vulnerability exists in WWBN AVideo, an open source video platform, specifically in versions 26.0 and prior. The issue is in the installation script install/deleteSystemdPrivate.php, which contains a PHP operator precedence bug in its command-line interface (CLI) access guard.
The script is intended to be run only from the command line, and it uses a condition to check this. However, the condition uses the expression !php_sapi_name() === 'cli', which due to PHP's operator precedence rules, always evaluates to false. This means the script's protection does not work as intended.
As a result, the script can be accessed via HTTP without authentication, allowing an attacker to delete files from the server's temporary directory and also see the contents of that directory in the response.
At the time of publication, no public patches are available to fix this issue.
How can this vulnerability impact me? :
This vulnerability can have several impacts:
- An attacker can access the installation script via HTTP without authentication.
- The attacker can delete files from the server's temporary directory, potentially disrupting normal operations or causing data loss.
- The attacker can also view the contents of the temporary directory, which may expose sensitive information.
Overall, this can lead to partial denial of service and information disclosure on the affected server.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves the install/deleteSystemdPrivate.php script being accessible via HTTP without authentication due to a PHP operator precedence bug. Detection would involve checking if this script is accessible remotely and if it discloses temp directory contents or deletes files.
You can attempt to detect the vulnerability by sending an HTTP request to the install/deleteSystemdPrivate.php script on your server and observing the response.
- Use a command like: curl -i http://yourserver/install/deleteSystemdPrivate.php
- If the script is accessible and returns temp directory contents or performs file deletion actions, the vulnerability is present.
Additionally, you can check your web server logs for any HTTP requests to install/deleteSystemdPrivate.php to identify if the script has been accessed.
What immediate steps should I take to mitigate this vulnerability?
Since there are no publicly available patches at the time of publication, immediate mitigation should focus on restricting access to the vulnerable script.
- Restrict HTTP access to install/deleteSystemdPrivate.php by configuring your web server to deny requests to this script.
- Remove or rename the install/deleteSystemdPrivate.php script if it is not needed.
- Implement firewall rules or access control lists to block external access to this script.
Monitor your server for any suspicious activity related to this script and review logs regularly.