Quick answers
- Is CVE-2026-45620 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45620 being exploited in the wild.
- How severe is CVE-2026-45620?
- Medium severity, with a CVSS score of 5.3, published 29 May 2026.
- Which products and versions are affected?
- wwbn/avideo (Packagist) <= 29.0, ECOSYSTEM:introduced=0,last_affected=29.0; WWBN AVideo <= 29.0.
- Is there a fix for CVE-2026-45620?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-45620 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-45620?
- Check whether you run wwbn/avideo (Packagist) or 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.
Technical details
An improper authorization vulnerability exists in WWBN AVideo versions 29.0 and earlier within the 'objects/mention.json.php' component. The script fails to implement 'User::loginCheck()' or any administrative access controls, relying solely on a regex check for a leading '@' character in the 'term' request parameter. This allows a remote, unauthenticated attacker to query the 'User::getAllUsers' method and retrieve sensitive user information including names, emails, and channel names. This issue is a sibling to CVE-2026-43881 and represents an incomplete fix in the codebase.
Affected products
- WWBN AVideo <= 29.0
Identifiers
- CVE-2026-45620
- GHSA-vpfx-pxqw-2w79
Timeline
- 2026-05-11: advisory: GitHub Security Advisory published
- 2026-05-29: disclosed: CVE published to NVD