Quick answers
- Is CVE-2026-43885 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-43885 being exploited in the wild.
- How severe is CVE-2026-43885?
- High severity, with a CVSS score of 4, published 11 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-43885?
- 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-43885 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-43885?
- 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
A sensitive information disclosure vulnerability exists in WWBN AVideo due to improper authorization checks in the 'objects/plugins.json.php' endpoint. This endpoint is publicly accessible and fails to redact the 'APISecret' stored within the 'object_data' field for unauthenticated requests. An attacker can retrieve this secret and use it as a valid authentication token for the 'plugin/API/get.json.php' endpoint. This allows the attacker to execute protected API calls, such as 'users_list', effectively bypassing authentication. A fix has been introduced in commit 1c36f229d0a103528fb9f64d0a1cc0e1e8f5999b.
Affected products
- WWBN AVideo <= 29.0
Identifiers
- CVE-2026-43885
- GHSA-xr49-f4rh-qcjf
Timeline
- 2026-04-27: advisory: GitHub Security Advisory published
- 2026-05-11: disclosed: CVE published to NVD