Summary
An authenticated Remote Code Execution (RCE) vulnerability was identified in AVideo related to the plugin upload/import functionality.
The issue allowed an authenticated administrator to upload a specially crafted ZIP archive containing executable server-side files. Due to insufficient validation of extracted file contents, the archive was extracted directly into a web-accessible plugin directory, allowing arbitrary PHP code execution.
Vulnerability Type
- Remote Code Execution (RCE)
- CWE-434: Unrestricted Upload of File with Dangerous Type
Affected Versions
- All versions up to and including 22.x.
Fixed Version
- A fix is expected to be released in version 23.
Root Cause
The system validated only the ZIP extension of uploaded plugin packages but did not enforce a strict allowlist of file types within the archive. Extracted files were placed directly in a web-accessible directory without preventing execution of server-side scripts.
Workarounds
If upgrade is not immediately possible:
- Disable plugin upload/import functionality.
- Configure the web server to prevent execution of PHP files inside plugin upload directories.
Impact
An authenticated administrator could execute arbitrary code on the server, resulting in full system compromise, including:
- Confidentiality loss
- Integrity loss
- Availability impact
The application accepts file uploads without adequately restricting the file type or content. Typical impact: remote code execution if the uploaded file can be served and executed on the server.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Upgrade immediately to AVideo version 23 or later.
Version 23 introduces improved validation and secure handling of plugin extraction.
Frequently Asked Questions
- What is CVE-2026-28502? CVE-2026-28502 is a critical-severity unrestricted upload of dangerous file types vulnerability in wwbn/avideo (composer), affecting versions < 21.0. No fixed version is listed yet. The application accepts file uploads without adequately restricting the file type or content.
- Which versions of wwbn/avideo are affected by CVE-2026-28502? wwbn/avideo (composer) versions < 21.0 is affected.
- Is there a fix for CVE-2026-28502? No fixed version is listed for CVE-2026-28502 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is CVE-2026-28502 exploitable, and should I be worried? Whether CVE-2026-28502 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
- What actually determines whether CVE-2026-28502 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.
- How do I fix CVE-2026-28502? No fixed version is listed yet. In the interim: Validate file type by inspecting the content, not just the extension or MIME type declared by the client. Store uploads outside the web root.