CVE-2026-126542

validatingZero is analyzing and reversing it now.
no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
WWBN AVideo >= 6.5, <= 29.7.1
CWE-290 Authentication Bypass by Spoofing
ETK-2026-4125Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

WWBN AVideo versions 6.5 through 29.7.1 are affected by an authentication bypass in the Hybridauth social-login flow. An unauthenticated attacker may sign in as an existing account, including an administrator, when a social identity has a display name matching that account's username and does not provide an email address.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Disable or restrict Hybridauth social login, especially X, Facebook, Yahoo, and LinkedIn providers, until a vendor update is available. Limit access to the application and review accounts and administrator sessions for unexpected logins.

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 00:58Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-11 00:58Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-126542

{
  "etk_id": "ETK-2026-4125",
  "cve_id": "CVE-2026-126542",
  "display_id": "CVE-2026-126542",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Authentication bypass in WWBN AVideo social login",
  "summary": "WWBN AVideo versions 6.5 through 29.7.1 are affected by an authentication bypass in the Hybridauth social-login flow. An unauthenticated attacker may sign in as an existing account, including an administrator, when a social identity has a display name matching that account's username and does not provide an email address.",
  "mitigation": "Disable or restrict Hybridauth social login, especially X, Facebook, Yahoo, and LinkedIn providers, until a vendor update is available. Limit access to the application and review accounts and administrator sessions for unexpected logins.",
  "vendor": "WWBN",
  "product": "AVideo",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 6.5, <= 29.7.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "AVideo",
      "purl": null
    }
  ],
  "cwes": [
    290
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-11T00:58:54.004000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T00:58:54.004000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T00:58:54.004000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-126542"
    }
  }
}

published 2026-11-11 01:21Z
last change 2026-11-11 01:21Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.