CVE-2026-12120
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe FireBox Popups WordPress plugin up to version 3.1.7 contains an Insecure Direct Object Reference (IDOR) vulnerability in the form_id parameter. Unauthenticated attackers can submit arbitrary form_id values to trigger CSV exports containing all form submission data, including any PII collected through those forms.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify FireBox Popups plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'FireBox Popups' or check the plugin files in /wp-content/plugins/firebox/ for the main PHP file to read the version headerAffected if The plugin is installed and the version is 3.1.7 or lower
-
Confirm installed version numberOpen the main plugin file (usually firebox.php or index.php in the plugin directory) and locate the Version header in the plugin comments, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name LIKE '%version%' AND option_name LIKE '%firebox%'Affected if Version is 3.1.7 or any version below it (e.g., 3.1.6, 3.1.5, etc.)
-
Check if plugin export functionality is accessibleTest access to the export endpoint by sending a GET request to /wp-admin/admin-ajax.php?action=firebox_export_csv&form_id=1 (or the actual export URL used by the plugin) without authenticationAffected if The export endpoint responds without requiring authentication and returns CSV data
-
Inspect access logs for export requestsReview web server access logs (Apache: /var/log/apache2/access.log, Nginx: /var/log/nginx/access.log) for requests to export-related URLs containing form_id parameters from unauthenticated IPsAffected if Unauthenticated requests to export endpoints with arbitrary form_id values appear in logs
A user is affected if the FireBox Popups plugin version is 3.1.7 or lower AND the export functionality is exposed without authentication, allowing anyone to access form submission data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the FireBox Popups plugin to the latest version once available, or disable and replace the plugin if no patch is released. Until fixed, monitor access logs for suspicious requests to export endpoints.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12120 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12120 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data