Quick answers
- Is CVE-2026-76610 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76610 being exploited in the wild.
- How severe is CVE-2026-76610?
- Informational severity, published 20 August 2026.
- Which products and versions are affected?
- YOOtheme Zoo < 4.1.65.
- Is there a fix for CVE-2026-76610?
- 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-76610 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-76610?
- Check whether you run YOOtheme Zoo 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
The vulnerability is an authorization bypass (missing ACL checks) in the Zoo comment controller endpoint. The comment controller fails to validate user permissions before processing tag modification requests, allowing any unauthenticated user to submit requests that modify tags on items. The attack is network-accessible and requires no authentication or special preconditions. An attacker can arbitrarily alter tag associations on Zoo items, affecting content categorization and discoverability. The issue is resolved in Zoo version 4.1.65 and later.
Affected products
- YOOtheme Zoo < 4.1.65
Timeline
- 2026-08-20: disclosed