Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as Author or Admin
-
ExploitAccess FireBox Form Display Condition setting
-
ExecutionInject SQL via unescaped parameter
-
ImpactExtract sensitive data from database
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account with the edit_fireboxes capability reaching the FireBox 'Form Display Condition' feature. On fresh installations of version 3.1.10 and later, this effectively means administrator-level access; on sites UPGRADED from a version prior to 3.1.10, the preserveCampaignRoleAccess() migration grants edit_fireboxes to any role that previously held edit_posts, lowering the requirement to Author-level - this upgrade history is the key enabling condition. Limiting factors: attacker must already be authenticated (PR:L minimum, PR:H on fresh installs), the plugin must be installed and ≤3.1.13, and exploitation complexity is high (AC:H). Impact is confined to confidentiality (data extraction); no integrity or availability impact. |
| Impact | This is a genuine but moderate-priority issue rather than an urgent fire. The CVSS 3.1 base score is 5.3 (Medium) with vector AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N, meaning network-reachable but with high attack complexity, requiring existing authenticated privileges, and impacting only confidentiality. The high confidentiality impact (C:H) reflects that SQL injection can extract sensitive database contents (password hashes, PII, secret keys), which is the primary concern. However, several factors sharply limit real-world risk: no EPSS score was supplied in the input, there is no CISA KEV listing, and no public exploit code is identified - exploitation status is therefore 'no public exploit identified at time of analysis.' The most important nuance is the privilege requirement: on fresh installations of 3.1.10 and later the attacker needs administrator-level access (a very high bar, since an admin can already read the database), which would arguably warrant PR:H and makes the practical impact low. The PR:L rating only holds on sites upgraded from a version prior to 3.1.10, where the preserveCampaignRoleAccess() migration erroneously grants the edit_fireboxes capability to any role that previously had edit_posts - lowering the bar to Author-level. The AC:H rating further reflects that exploitation depends on this specific migration state. Net assessment: real but conditional priority - patch promptly on upgraded multi-author sites, lower urgency on fresh single-admin installs. |
| Exploit ScenarioDerived | An attacker who holds an Author-level account on a WordPress site that was upgraded from a FireBox version prior to 3.1.10 (where the edit_fireboxes capability was mistakenly granted to edit_posts roles) crafts a malicious value in the FireBox Form Display Condition. Because the user-supplied parameter is insufficiently escaped and the SQL query is not properly prepared, the attacker appends additional SQL to extract password hashes, user data, or API keys from the database. No public exploit code has been identified, and on fresh 3.1.10+ installs the same attack requires administrator access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Authenticated SQL injection in the FireBox - WooCommerce Popup Builder, Exit Intent Popup, Email Optin & Cart Abandonment plugin for WordPress (all versions up to and including 3.1.13) lets a user holding the edit_fireboxes capability append arbitrary SQL to the plugin's Form Display Condition query and read sensitive data from the site database. Because the preserveCampaignRoleAccess() migration on sites upgraded from before 3.1.10 grants edit_fireboxes to any role that previously held edit_posts, exploitation is possible at Author level on upgraded installations, while fresh installs from 3.1.10 onward require administrator access. The issue is rated CVSS 5.3 (AC:H, PR:L, confidentiality-only) and no public exploit identified at time of analysis.
RemediationAI
Apply the vendor fix: an upstream fix is available in the FireBox plugin trunk via changeset 3724861 (https://plugins.trac.wordpress.org/changeset/3724861/firebox/trunk/Inc/Framework/Inc/Base/Conditions/Conditions/FireBox/Form.php) and should be included in the next plugin release after 3.1.13, but a released patched version is not independently confirmed here, so verify the plugin's changelog and update to a version that contains that change before relying on it. If an update is not yet installable, the most direct mitigation is to restrict the edit_fireboxes capability: remove it from Author, Contributor and any non-administrator roles, and audit roles on sites that were upgraded from a FireBox version earlier than 3.1.10 because the preserveCampaignRoleAccess() migration may have silently granted it to every role that previously had edit_posts - the trade-off is that legitimate non-admin campaign managers lose access to FireBox campaign editing. Deactivating or removing the plugin eliminates the exposure entirely but disables popups and campaign features, and general WordPress hardening such as limiting author-level accounts, keeping the plugin updated, and monitoring database activity can reduce the window while a patched release is rolled out. Consult the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/cc07d2db-0a1b-4948-ad02-f9b244b40e66?source=cve for vendor-supplied version details.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-89, an SQL injection in the FireBox WordPress plugin's Form Display Condition handling, where a user-supplied parameter reaches a query without sufficient escaping and the existing statement is not prepared. Wordfence's report points to the affected code paths in the plugin's condition class (Inc/Framework/Inc/Base/Conditions/Conditions/FireBox/Form.php, around line 46) and its database layer (Inc/Framework/Inc/Includes/DB.php, around line 198), with related handling in Inc/Core/FB/Meta.php (around line 411) in tag 3.1.13. WordPress stores plugin data in the site's MySQL/MariaDB database, so injected SQL runs with the WordPress database user's privileges, allowing data in WordPress and plugin tables to be read. Access is gated by the plugin's edit_fireboxes capability; the preserveCampaignRoleAccess() migration introduced in 3.1.10 is the key condition that widens who holds that capability on upgraded sites, while fresh installations from 3.1.10 onward keep the capability at administrator level. The CVSS vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N) confirms a network-reachable, authenticated, high-complexity bug with confidentiality-only impact and no integrity or availability effect.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Network-reachable injection but gated behind authenticated edit_fireboxes access (PR:L on upgraded sites) and dependent on migration state (AC:H); data-extraction only yields C:H with I:N/A:N.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The FireBox - WooCommerce Popup Builder, Exit Intent Popup, Email Optin & Cart Abandonment plugin for WordPress is vulnerable to generic SQL Injection via FireBox Form Display Condition in all versions up to, and including, 3.1.13 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with author-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. On fresh installations of version 3.1.10 and later, exploitation requires administrator-level access; however, on sites upgraded from a version prior to 3.1.10, the preserveCampaignRoleAccess() migration grants the edit_fireboxes capability to any role that previously held edit_posts, reducing the minimum required privilege to Author-level.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-96066
GHSA-8cc4-h37g-8v64
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB