HomeWordPress vulnerabilitiesFireBox
FireBox vulnerabilities
FireBox has 2 known vulnerabilities in this database. The most recent published record is dated 9 Sep 2026.
- Known vulnerabilities
- 2
- Active installs
- 7,000+
- Latest version
- 3.1.13
- Last updated
- 7 Sep 2026
- Most recent
- 9 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2026-76801 | High 8.8 | Up to 3.1.10 | Fixed in a later version (latest 3.1.13) | 9 Sep 2026 |
| Sensitive data exposure CVE-2026-12120 | Medium 5.3 | Up to 3.1.7 | Fixed in a later version (latest 3.1.13) | 18 Jun 2026 |
Read the published descriptions
- CVE-2026-76801, 9 Sep 2026
- The FireBox - WooCommerce Popup Builder, Exit Intent Popup, Email Optin & Cart Abandonment plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 3.1.10 via the value function. This is due to a trivially bypassable regex blacklist in Executer::allowedToRun() that fails to block WordPress core functions such as wp_insert_user, update_option, and file_put_contents, combined with no sanitization of PHP condition rule values stored via the firebox_meta REST endpoint. This makes it possible for authenticated attackers, with author-level access and above, to execute code on the server. On sites upgraded from a version prior to 3.1.10, the Migrator::preserveCampaignRoleAccess() function automatically grants the edit_fireboxes and publish_fireboxes capabilities to the Author role, lowering the effective entry point to Author-level access. CVE record
- CVE-2026-12120, 18 Jun 2026
- The FireBox Popups - Increase Sales and Grow Your Email List plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.1.7 via the 'form_id' parameter. This makes it possible for unauthenticated attackers to extract download a full CSV export of all form submissions - including any personally identifiable information submitted by users - for any arbitrary form_id. CVE record
What to do if you run FireBox
If you run FireBox, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new FireBox vulnerabilities
Free. We email you when a new vulnerability is published for FireBox, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.