Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-28501: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in WWBN AVideo

0
Critical
VulnerabilityCVE-2026-28501cvecve-2026-28501cwe-89
Published: Fri Mar 06 2026 (03/06/2026, 03:05:21 UTC)
Source: CVE Database V5
Vendor/Project: WWBN
Product: AVideo

Description

CVE-2026-28501 is a critical SQL Injection vulnerability in WWBN AVideo versions prior to 24. 0. It affects the objects/videos. json. php and objects/video. php components, where the catName parameter is improperly sanitized when supplied via a JSON-formatted POST request. The vulnerability arises because JSON input is parsed and merged into $_REQUEST after global security checks, allowing attackers to bypass sanitization. This flaw enables unauthenticated attackers to execute arbitrary SQL commands, potentially compromising confidentiality, integrity, and availability of the backend database. The vulnerability has been patched in version 24. 0.

AI-Powered Analysis

AILast updated: 03/06/2026, 03:46:06 UTC

Technical Analysis

CVE-2026-28501 is a critical SQL Injection vulnerability identified in the open-source video platform WWBN AVideo, specifically affecting versions prior to 24.0. The vulnerability exists in the objects/videos.json.php and objects/video.php components, where the application fails to properly sanitize the 'catName' parameter when it is provided via a JSON-formatted POST request body. The root cause is that JSON input is parsed and merged into the PHP $_REQUEST superglobal after global security checks have been executed. This sequence allows maliciously crafted SQL injection payloads to bypass existing sanitization and validation mechanisms. Because the vulnerability is exploitable without authentication (AV:N/PR:N/UI:N), an attacker can remotely inject arbitrary SQL commands, potentially leading to unauthorized data disclosure, data modification, or deletion, and even full compromise of the backend database. The vulnerability impacts confidentiality, integrity, and availability of data stored by the application. The issue has been addressed and patched in version 24.0 of AVideo. Although no known exploits are currently reported in the wild, the critical CVSS score of 9.8 reflects the high risk posed by this vulnerability.

Potential Impact

The SQL Injection vulnerability in WWBN AVideo can have severe consequences for organizations using affected versions. An unauthenticated attacker can execute arbitrary SQL commands on the backend database, leading to unauthorized access to sensitive user data, including video metadata and potentially user credentials if stored in the database. Attackers could modify or delete video content records, disrupt service availability, or escalate attacks to compromise the underlying server infrastructure. This can result in data breaches, loss of user trust, regulatory penalties, and operational downtime. Given that AVideo is an open-source platform used globally for video hosting and streaming, organizations relying on it for content delivery or internal video management are at significant risk. The ease of exploitation and lack of authentication requirements increase the likelihood of attacks, especially in environments where the platform is exposed to the internet without additional protective controls.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately upgrade WWBN AVideo to version 24.0 or later, where the issue is patched. Until the upgrade can be performed, implement web application firewall (WAF) rules specifically designed to detect and block SQL injection attempts targeting the 'catName' parameter in JSON POST requests. Review and harden input validation mechanisms to ensure JSON inputs are sanitized before merging into $_REQUEST or similar global variables. Disable or restrict access to the affected endpoints (objects/videos.json.php and objects/video.php) from untrusted networks if possible. Conduct thorough code audits to verify no other parameters or endpoints are vulnerable to similar injection flaws. Additionally, monitor application logs for suspicious SQL syntax or unexpected database errors that could indicate exploitation attempts. Employ database least privilege principles to limit the impact of any successful injection.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-27T20:57:47.708Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69aa4a7bc48b3f10ffe32f79

Added to database: 3/6/2026, 3:31:07 AM

Last enriched: 3/6/2026, 3:46:06 AM

Last updated: 3/6/2026, 6:36:00 AM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses