FireBox at a glance
- 4 publicly disclosed vulnerabilities, 1 of them rated High or Critical. The most recent was disclosed on Oct 9, 2026.
- Ranked #2747 by popularity on WordPress.org (6,000+ active installs).
- The latest version is 3.1.17 (released Nov 16, 2026). The most recent security fix shipped in 3.1.14.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your FireBox version
Enter the FireBox version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “FireBox”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “FireBox”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (3.1.17). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known FireBox vulnerabilities
FireBox <= 3.1.13 - Authenticated (Author+) SQL Injection via FireBox Form Display Condition
SQL injection · CVE-2026-104724
Affected versions: ≤ 3.1.13
Fixed in: 3.1.14
Severity: Medium 5.3 · Disclosed Oct 9, 2026
FireBox <= 3.1.10 - Authenticated (Author+) Remote Code Execution to Privilege Escalation
Remote code execution · CVE-2026-76801
Affected versions: ≤ 3.1.10
Fixed in: 3.1.11
Severity: High 8.8 · Disclosed Sep 8, 2026
FireBox Popups <= 3.1.7 - Unauthenticated Sensitive Information Exposure in 'form_id' Parameter
Information disclosure · CVE-2026-12120
Affected versions: ≤ 3.1.7
Fixed in: 3.1.8
Severity: Medium 5.3 · Disclosed Jun 17, 2026
FireBox <= 3.1.0-free - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2025-67545
Affected versions: ≤ 3.1.0-free
Fixed in: 3.1.1-free
Severity: Medium 6.4 · Disclosed Nov 27, 2025
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| FireBox <= 3.1.13 - Authenticated (Author+) SQL Injection via FireBox Form Display ConditionSQL injection · CVE-2026-104724 | ≤ 3.1.13 | 3.1.14 | Medium 5.3 | Oct 9, 2026 |
| FireBox <= 3.1.10 - Authenticated (Author+) Remote Code Execution to Privilege EscalationRemote code execution · CVE-2026-76801 | ≤ 3.1.10 | 3.1.11 | High 8.8 | Sep 8, 2026 |
| FireBox Popups <= 3.1.7 - Unauthenticated Sensitive Information Exposure in 'form_id' ParameterInformation disclosure · CVE-2026-12120 | ≤ 3.1.7 | 3.1.8 | Medium 5.3 | Jun 17, 2026 |
| FireBox <= 3.1.0-free - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2025-67545 | ≤ 3.1.0-free | 3.1.1-free | Medium 6.4 | Nov 27, 2025 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 9, 2026.
Most common weaknesses in FireBox
SQL injection
1 issue
Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.
Remote code execution
1 issue
An attacker can run code of their choice on your server. This is the most dangerous kind: it usually means a full takeover of the site.
Information disclosure
1 issue
Data that should stay private, such as user details or configuration values, can be read from outside.
Frequently asked questions
Is FireBox safe to use?
FireBox is a well-known plugin with 6,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.1.17) and turn on automatic updates.
How do I find which version of FireBox my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.