Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-85155 – Unauthenticated SQL Injection (Ordering Oracle) – WWBN AVideo ≤ current (commit e01

Be the first to know when new zero-days emerge:

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=channels specifying a column such as users.password or users.recoverPass as 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 e01e41ecc and 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 referencing users.password or users.recoverPass or 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(

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge