Summary
AVideo affected by unauthenticated application takeover via exposed web installer on uninitialized deployments
Impact
- Full application takeover: Attacker becomes the sole admin with complete control
- Persistent backdoor via configuration: The
videos/configuration.phpfile is written with attacker-controlled database credentials, ensuring persistent access even after the attack - Data exfiltration: If pointing to the attacker's database, all future user data (registrations, uploads, comments) flows to the attacker
- Remote code execution potential: Admin access in AVideo enables file uploads and plugin management, which can lead to arbitrary PHP execution
- SQL injection bonus:
$_POST['contactEmail']on line 120 is directly concatenated into SQL, allowing additional database manipulation
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
CVE-2026-33038 has a CVSS score of 8.1 (High). 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.
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
In the interim: Keep the dependency up to date. Add authentication gating to all sensitive endpoints.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-33038? CVE-2026-33038 is a high-severity missing authentication for critical function vulnerability in wwbn/avideo (composer), affecting versions <= 25.0. No fixed version is listed yet. A critical operation is accessible without requiring any authentication.
- How severe is CVE-2026-33038? CVE-2026-33038 has a CVSS score of 8.1 (High). 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.
- Which versions of wwbn/avideo are affected by CVE-2026-33038? wwbn/avideo (composer) versions <= 25.0 is affected.
- Is there a fix for CVE-2026-33038? No fixed version is listed for CVE-2026-33038 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is CVE-2026-33038 exploitable, and should I be worried? Whether CVE-2026-33038 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-33038 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-33038? No fixed version is listed yet. In the interim: Keep the dependency up to date. Add authentication gating to all sensitive endpoints.