Summary
CVE-2026-85155 is a SQL injection vulnerability in WWBN AVideo affecting the get.json.php API endpoint when called with APIName=channels. An unauthenticated attacker can control the sort-column parameter of the underlying query, allowing arbitrary database columns—including sensitive user table fields—to be used for result ordering. The issue is rated high severity due to its unauthenticated network attack vector and resulting sensitive information exposure.
Technical details
- Root cause: the endpoint sanitizes the sort parameter with a character filter (
preg_replace("/[^A-Za-z0-9._ ]/", '', $key)) that strips SQL syntax characters but does not validate that the supplied value is an allowed/expected column name. - Trigger condition: an attacker sends a request to
/plugin/API/get.json.php?APIName=channelsspecifying a column such asusers.passwordorusers.recoverPassas the sort key. - Attack vector: network, no authentication or user interaction required.
- Impact: the response ordering acts as an oracle that leaks information about password hashes and password-recovery tokens; supplying invalid column names triggers a database error (MySQL error 1054) that discloses the full SQL query and portions of the database schema.
Affected software
- WWBN AVideo, current version at commit
e01e41eccand earlier — no patched version is currently available.
Severity
- CVSS score: 8.7
- A separately reported CVSS v3.1 vector for this issue is
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N(7.5, High).
Mitigation and recommended actions
- Immediate: no vendor patch is currently available; monitor the WWBN AVideo GitHub security advisories for a fixed release and upgrade as soon as one is published.
- Workarounds: restrict or disable public/unauthenticated access to
/plugin/API/get.json.php(e.g., via reverse proxy, WAF rule, or authentication gating) until a fix is released; block requests that pass non-standard values in sort/order parameters; monitor logs for repeated requests referencingusers.passwordorusers.recoverPassor for database error disclosures in API responses.
How IONIX identifies potentially affected assets
IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Page title:
Sign In - AVideo,AVideo - Raw response body:
id="avideoModal",avideoAlert(,avideoModalIframe(

