CVE-2026-28501

Workarounds

There is no reliable workaround.

The only recommended mitigation is to upgrade immediately to version 23 upon its release.

References

Internal security report.

An unauthenticated SQL Injection vulnerability exists in AVideo within the objects/videos.json.php and objects/video.php components.

The application fails to properly sanitize the catName parameter when it is supplied via a JSON-formatted POST request body. Because JSON input is parsed and merged into $_REQUEST after global security checks are executed, the payload bypasses the existing sanitization mechanisms.

This allows an unauthenticated attacker to:

• Execute arbitrary SQL queries
• Perform full database exfiltration
• Extract sensitive data including administrator usernames, password hashes, session identifiers and user records
• Potentially escalate privileges by cracking password hashes offline
• Chain with authenticated vulnerabilities to achieve full system compromise

This vulnerability is classified as:

• CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2026-28501 has a CVSS score of 9.8 (Critical). 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.

Kodem intelligence

This vulnerability has been fixed in version 23.

Users must upgrade to version 23 or later.

1. What is CVE-2026-28501? CVE-2026-28501 is a critical-severity SQL injection vulnerability in wwbn/avideo (composer), affecting versions <= 21.0.0. No fixed version is listed yet. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2026-28501? CVE-2026-28501 has a CVSS score of 9.8 (Critical). 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.
3. Which versions of wwbn/avideo are affected by CVE-2026-28501? wwbn/avideo (composer) versions <= 21.0.0 is affected.
4. Is there a fix for CVE-2026-28501? No fixed version is listed for CVE-2026-28501 yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is CVE-2026-28501 exploitable, and should I be worried? Whether CVE-2026-28501 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
6. What actually determines whether CVE-2026-28501 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.
7. How do I fix CVE-2026-28501? No fixed version is listed yet. In the interim: Use parameterized queries or prepared statements so user input is always treated as data, never as SQL syntax.