/

CVE-2026-85155

Severity:

HIGH RISK

(7.5)

SQL Injection (CWE-89) in AVideo Channels API Endpoint

CVE-2026-85155

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Sensitive Data Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

WWBN AVideo contains a SQL injection vulnerability in the sort-column parameter of the channels API endpoint. An unauthenticated attacker may use the ordering behavior and database errors to infer sensitive password hashes, recovery tokens, query details, and schema information.

Affected context

The issue occurs in deployments where the get.json.php endpoint is reachable and processes requests for APIName=channels. Risk depends on whether the sort-column parameter is incorporated into database queries without strict allowlisting and whether database errors or result-ordering behavior are observable to callers.

Exploit preconditions

  • Attack surface: The publicly reachable channels API endpoint
  • Required access: No authentication may be required when the endpoint is exposed
  • Trigger point: Processing of the user-controlled sort-column parameter
  • Why exploitation is possible: Untrusted input can influence query construction, allowing database behavior and errors to reveal information beyond the intended result set

Why this happens

The vulnerability results from incorporating a user-controlled sorting expression into a SQL statement without restricting it to a predefined set of valid column names. This is a form of CWE-89: SQL Injection, in which application input changes database query structure rather than being treated solely as data. Observable ordering behavior and verbose SQL errors can amplify the disclosure risk.

Potential impact

  • Attackers may infer password hash values or account recovery tokens
  • Database schema and query details could be disclosed through error responses
  • Sensitive records may become easier to enumerate or target
  • Application confidentiality and account security could be weakened
  • Downstream compromise may be possible if exposed credentials or tokens are reusable

General mitigation guidance

Mitigation generally focuses on separating query structure from user-provided values and reducing information exposed by database interactions.

Common defensive patterns include:

  • Mapping accepted sort options to a fixed server-side allowlist of column identifiers
  • Rejecting unknown, malformed, or unexpected sort parameters by default
  • Using parameterized queries for data values and avoiding dynamic SQL identifiers
  • Returning generic application errors instead of raw database statements or schema details
  • Limiting database account privileges and restricting access to sensitive credential fields
  • Treating password hashes and recovery tokens as sensitive data with narrowly scoped access

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis rules identifying string concatenation or interpolation in SQL construction
  • Code review checks for dynamic ORDER BY clauses and unvalidated identifier parameters
  • Tests that submit unexpected sort values and verify rejection without database errors
  • Web application monitoring for repeated requests that vary sorting parameters or provoke SQL errors
  • Policy enforcement requiring parameterized queries and allowlisted database identifiers
  • Neutral automated security review tools that flag injection-prone query-building patterns

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-pmmj-6425-gpgh
vulncheck.comvulncheck.com/advisories/wwbn-avideo-sql-injection-via-get-json-php-apiname-channels

Frequently asked

questions

It may be remotely exploitable when the channels API is publicly reachable and accepts unauthenticated requests.

No authenticated account may be necessary, but the attacker must be able to reach the affected endpoint and observe its responses.

Restrict sorting to a server-side allowlist of known-safe column mappings and keep dynamic SQL identifiers separate from user-controlled input.

Combine parameterized database access, strict input validation, generic error handling, least-privilege database accounts, and testing for injection in API parameters.

Find out what's already
exploitable in your codebase.