Brave Popup Builder <= 0.7.0 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 0.7.1
- Affected Plugin
- Brave – Create Popup, Optins, Lead Generation, Survey, Sticky Elements & Interactive Content
- Affected Version
<= 0.7.0- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-43337
At a glance
CVE-2024-43337 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Brave WordPress plugin, affecting versions <= 0.7.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 0.7.1; sites on affected versions should update now. Disclosed August 2024, reported by Ananda Dhakal.
Vulnerability Overview
The Brave Popup Builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 0.7.0. This is due to missing or incorrect nonce validation on the bravepop_ajax_zoho_init_token() function. This makes it possible for unauthenticated attackers to save an integration token via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Brave <= 0.7.0 carries this weakness at bravepop_ajax_zoho_init_token(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Brave the fix is 0.7.1: builds <= 0.7.0 are affected, anything from 0.7.1 onward is not.
Remediation
Update to version 0.7.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Brave: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Brave 0.7.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Brave – Create Popup, Optins, Lead Generation, Survey, Sticky Elements & Interactive Content
- 7.2CVE-2024-30453: Brave Popup Builder <= 0.6.5 SSRF
CVE-2024-30453 - 6.1CVE-2026-77115: Brave Reflected XSS
CVE-2026-77115 - 5.3CVE-2025-68508: Brave <= 0.8.3 Missing Authorization
CVE-2025-68508 - 4.4CVE-2024-35655: Brave Stored XSS
CVE-2024-35655 - 4.4CVE-2023-51534: Brave Popup Builder <= 0.6.2 Stored XSS
CVE-2023-51534 - 4.3CVE-2026-77116: Brave Popup Builder <= 0.8.5 IDOR
CVE-2026-77116
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C