CVE-2026-28501: WWBN AVideo: Unauthenticated SQL Injection via JSON Request Bypass in objects/videos.json.php

Published Mar 2, 2026
·
Updated

Impact

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)

Patches

This vulnerability has been fixed in version 23.

Users must upgrade to version 23 or later.

Workarounds

There is no reliable workaround.

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

References

Internal security report.

Other sources

WWBN AVideo is an open source video platform. Prior to version 24.0, 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 issue has been patched in version 24.0.

MITRE

Affected Software

2 affected components
composer/wwbn/avideo<=21.0.0
WWBN AVideo<24.0

Event History

Mar 2, 2026
Advisory Published
via GitHub·08:49 PM
Data Sourced
via GitHub·08:49 PM
DescriptionSeverityWeaknessAffected Software
Mar 6, 2026
CVE Published
via MITRE·03:05 AM
Data Sourced
via MITRE·03:05 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 AM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-28501?

CVE-2026-28501 is classified as a high severity vulnerability due to the potential for unauthenticated SQL injection.

2

How do I fix CVE-2026-28501?

To fix CVE-2026-28501, upgrade AVideo to version 21.0.1 or later, where the vulnerability has been addressed.

3

Who is affected by CVE-2026-28501?

CVE-2026-28501 affects users of AVideo versions up to and including 21.0.0.

4

What components of AVideo are involved in CVE-2026-28501?

CVE-2026-28501 involves the components objects/videos.json.php and objects/video.php in AVideo.

5

Is user authentication necessary to exploit CVE-2026-28501?

No, CVE-2026-28501 can be exploited without user authentication, allowing unauthenticated users to perform SQL injection.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203