Quick answers
- Is CVE-2026-77116 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77116 being exploited in the wild.
- How severe is CVE-2026-77116?
- Medium severity, with a CVSS score of 4.3, published 23 August 2026.
- Which products and versions are affected?
- Brave Popup Builder through 0.8.5.
- Is there a fix for CVE-2026-77116?
- A patch was published on 2026-08-23: Fixed in version 0.8.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77116 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-77116?
- Check whether anything you run is named in the advisory. 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 IDOR (Insecure Direct Object Reference) / broken object-level access control issue in the bravepop_render_popup() function in lib/render.php. The preview feature checks only is_user_logged_in() when the brave_popup query parameter is present, performing no capability check, post status validation, or object ownership verification. An authenticated Subscriber or WooCommerce Customer can supply any popup post ID in the URL and retrieve rendered content regardless of post status (draft, pending, private, scheduled) or audience targeting rules. The vulnerability is a separate code path from the previously fixed CVE-2025-68508 (patched in 0.8.4), which affected an unauthenticated AJAX handler. This GET preview branch requires authentication but lacks the capability gates added to that handler. Fixed in version 0.8.6.
Affected products
- Brave Popup Builder through 0.8.5
Timeline
- 2026-08-23: disclosed
- 2026-08-23: patched: Fixed in version 0.8.6