Unauthenticated code execution via permitted PHAR files
Published Jul 24, 2025 · Updated Nov 3, 2025
Code execution in WWBN AVideo 14.4 and dev commit 8a8954ff allows remote attackers to run PHP via a requested .phar file. The generated videos/.htaccess blacklist matches PHP and other executable extensions but omits .phar, allowing Apache to pass PHP archives to the interpreter. Exploitation requires an attacker-controlled .phar file in the videos directory and a PHP environment with PHAR execution enabled, as in the default Docker configuration.
Summary
What happened
Code execution in WWBN AVideo 14.4 and dev commit 8a8954ff allows remote attackers to run PHP via a requested .phar file. The generated videos/.htaccess blacklist matches PHP and other executable extensions but omits .phar, allowing Apache to pass PHP archives to the interpreter. Exploitation requires an attacker-controlled .phar file in the videos directory and a PHP environment with PHAR execution enabled, as in the default Docker configuration.
The record
- CVE
- CVE-2025-48732
- Published
- Jul 24, 2025
- Updated
- Nov 3, 2025
- Vendor
- WWBN
- Product
- AVideo
- Classifications
- CWE-184, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 24, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=14.4
- Affected versionversion=dev master commit 8a8954ff
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo