Is CVE-2026-126544 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-126544 being exploited in the wild.

How severe is CVE-2026-126544?

Medium severity, with a CVSS score of 4.3, published 11 November 2026.

Which products and versions are affected?

WWBN AVideo 6.5 through 29.7.1.

Is there a fix for CVE-2026-126544?

Yes: fixed in 29.7.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-126544 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-126544?

Check whether you run WWBN AVideo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-126544: WWBN AVideo email verification bypass in User::verifyCode()

CVE-2026-126544 · Severity: medium · CVSS 4.3 · Published 2026-11-11

WWBN AVideo is a video hosting and streaming platform. A registered user can bypass email verification for any other account by reusing the installation-wide salt from their own verification link, enabling them to unlock premium features like live streaming on compromised accounts without the victims' knowledge.

Technologies: WWBN AVideo. Vendors: WWBN.

Quick answers

Is CVE-2026-126544 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-126544 being exploited in the wild.
How severe is CVE-2026-126544?: Medium severity, with a CVSS score of 4.3, published 11 November 2026.
Which products and versions are affected?: WWBN AVideo 6.5 through 29.7.1.
Is there a fix for CVE-2026-126544?: Yes: fixed in 29.7.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-126544 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-126544?: Check whether you run WWBN AVideo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 29.7.2 or later

Technical details

The vulnerability exists in User::verifyCode() in objects/user.php due to PHP loose comparison of the recoverPass token. An authenticated attacker can craft a verification code with an arbitrary users_id and recoverPass flag set to true, exploiting the predictable salt-based token validation. This allows account takeover of any user's email verification status without authentication.

Affected products

WWBN AVideo 6.5 through 29.7.1

Timeline

2026-11-11: disclosed
2026-11-11: patched: Fix improves validation and error logging in email verification process

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.