Secuno
ENNL
Book demo

CVE-2026-92578

8.1 HIGH
  1. Published16 Sept 2026

Description

WWBN AVideo through 29.0 contains an authentication bypass vulnerability where the stored password hash is accepted as a valid login credential through two independent code paths in loginFromRequest() and encryptPasswordVerify(). Attackers who obtain the stored users.password hash value can authenticate as any user by submitting the hash directly to login endpoints, completely bypassing password verification.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityHigh
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-634729.1
Vendure is an open-source headless commerce platform. Prior to 3.7.0,…
CVE-2026-929148.1
AVideo LoginControl contains an authentication bypass vulnerability in the PGP second…
CVE-2026-867109.8
The Login with QR WordPress plugin through 1.0.0 does not verify that the code used to…
CVE-2026-867099.8
The Pressengine WordPress plugin through 1.0 does not stop its login handler from…
CVE-2026-867079.8
The Private Feed Key WordPress plugin through 0.1 does not verify that the key used to…
CVE-2025-439368.1
Dell ObjectScale, versions prior to ObjectScale 4.4.0.0, contains an Improper…

Frequently asked

Is CVE-2026-92578 being actively exploited?

CVE-2026-92578 is not in the CISA KEV catalog.

How severe is CVE-2026-92578?

CVE-2026-92578 has a CVSS 3.1 base score of 8.1, rated high.

How do I fix CVE-2026-92578?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-92578 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.