/

CVE-2026-89242

Severity:

HIGH RISK

(7.2)

Server-Side Request Forgery (CWE-918) in WWBN AVideo Login

CVE-2026-89242

Deferred

Vulnerability type

Category:

Server-Side Request Forgery

CWE:

CWE-918

Impact:

Unauthorized Local File Read and Internal Service Access

Severity:

HIGH RISK

(7.2)

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

A server-side request forgery vulnerability in WWBN AVideo allows unauthenticated requests to make the server fetch attacker-supplied HTTP URLs or local file paths through the login handling flow. Retrieved content may be interpreted as login credentials, potentially exposing sensitive files or providing access to internal services.

Affected context

The vulnerability occurs in deployments where the _json_decode function processes attacker-influenced input and permits remote URL or local file retrieval without validating the destination. The affected login endpoint may be reachable without authentication, making the issue especially relevant when the AVideo server can access sensitive local paths or otherwise restricted internal network services.

Exploit preconditions

  • Attack surface: The unauthenticated login request-processing endpoint
  • Required access: Ability to send HTTP requests to the exposed AVideo service
  • Trigger point: Processing of attacker-controlled input by the _json_decode function
  • Why exploitation is possible: The server retrieves supplied URLs or file paths without enforcing SSRF destination controls, and the resulting content is processed as authentication-related data

Why this happens

The underlying bug is an unvalidated server-side fetch operation. Application-controlled input is treated as a trusted resource reference, allowing the server to access destinations selected by an external requester.

This maps to CWE-918: Server-Side Request Forgery, where an application can be induced to send requests to unintended network locations or access local resources. The absence of destination validation, protocol restrictions, and trust-boundary enforcement creates the insecure pattern.

Potential impact

  • An attacker may read sensitive local files accessible to the AVideo process
  • An attacker could query internal services that are not exposed publicly
  • Retrieved data may disclose credentials, tokens, or configuration details
  • Internal service responses could support further unauthorized access
  • The application may expose authentication-related data or enable account compromise

General mitigation guidance

Mitigation generally focuses on eliminating unnecessary server-side fetching and reducing trust in user-controlled resource references.

Common defensive patterns include:

  • Allowing only explicitly approved destinations and schemes
  • Rejecting local file references, loopback targets, link-local addresses, private networks, and other sensitive address ranges
  • Resolving hostnames safely and validating the final destination after redirects
  • Separating authentication parsing from network and filesystem access
  • Returning only the minimum necessary response data
  • Running the application with least-privilege filesystem and network permissions
  • Applying egress controls so the service cannot freely reach internal infrastructure
  • Using secure-by-default parsers and narrowly defined input schemas

How teams detect issues like this

Organizations can look for SSRF risks through:

  • Static analysis rules identifying user-controlled values passed to HTTP clients, URL handlers, or filesystem APIs
  • Code review checks for unrestricted URL schemes, redirects, hostname resolution, and local path handling
  • Runtime monitoring of unexpected outbound requests from the AVideo process
  • Network policy alerts for connections to loopback, private, link-local, metadata, or administrative service ranges
  • Web application logs showing unusual login endpoint requests or repeated attempts to access internal destinations
  • Policy enforcement requiring explicit URL allowlists and controlled egress for server-side fetch operations

Automated security review tools may help identify untrusted input reaching network or file access functions, but findings should be validated against deployment-specific trust boundaries.

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-wqwf-wmvx-53jh
vulncheck.comvulncheck.com/advisories/wwbn-avideo-unauthenticated-ssrf-via-login-json-php

Frequently asked

questions

Yes. The affected login-processing endpoint may accept unauthenticated HTTP requests, so exploitation can be remote when the AVideo service is reachable and the vulnerable code path is enabled.

The attacker generally needs network access to the AVideo endpoint but not a valid account. The server must also be able to reach or read the requested destination.

Prevent user-controlled input from selecting arbitrary URLs or file paths. If server-side retrieval is required, use strict allowlists, block sensitive address ranges and local resources, validate redirects, and enforce network egress restrictions.

Treat all externally supplied resource references as untrusted, separate authentication logic from resource fetching, apply least privilege, and monitor outbound connections from application services.

Find out what's already
exploitable in your codebase.