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

Back
New CVE Detected

CVE-2026-86190 – Unauthenticated Sensitive Data Exposure / Session Hijacking – WWBN AVideo ≤ 29.0

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-86190 is a broken access control vulnerability in WWBN AVideo affecting versions 0 through 29.0. The videoViewsInfo endpoints, when queried with a hash parameter, return complete user and viewer-session records — including password hashes, password-recovery tokens, and live session identifiers — to unauthenticated callers. The issue is rated critical, and the exposed session identifiers can be replayed to hijack viewer and administrator sessions.

Technical details

  • Root cause: videoViewsInfo.php / videoViewsInfo.json.php / videoViewsInfo.csv.php perform an authorization check (Video::canEdit()) only for requests using the videos_id parameter; requests using the hash parameter skip this check entirely.
  • The underlying database query selects the full user and video-statistics tables (SELECT u.*, vs.*) and serializes the result directly to JSON, exposing dozens of fields per viewer, including credentials, recovery tokens, contact/personal details, and the session_id.
  • Attack vector: network, no authentication or user interaction required (CVSS AV:N/AC:L/PR:N/UI:N).
  • Impact: disclosure of password hashes and recovery tokens, and theft of live session identifiers that can be replayed under the application’s session cookie to impersonate viewers, including administrators — leading to full account and site compromise.

Affected software

  • WWBN AVideo, all versions from 0 through 29.0

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • CVSS v4.0 Base Score: 9.3 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: at time of publication no patched AVideo release was confirmed; check the WWBN/AVideo GitHub repository for an update that restricts videoViewsInfo responses to non-sensitive fields (e.g., id, name, user, channelName, photoURL) and removes session_id from serialized output, and apply it as soon as it is released.
  • If no patch is available: restrict or disable public access to view/videoViewsInfo.php, view/videoViewsInfo.json.php, and view/videoViewsInfo.csv.php at the web server/proxy layer for unauthenticated requests using the hash parameter; rotate session secrets and force re-authentication for all active sessions; monitor logs for anomalous requests to these endpoints containing a hash parameter.

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge