Bit integrations at a glance
- 5 publicly disclosed vulnerabilities, 4 of them rated High or Critical. The most recent was disclosed on Oct 13, 2026.
- Ranked #1254 by popularity on WordPress.org (20,000+ active installs).
- The latest version is 2.11.1 (released Nov 16, 2026). The most recent security fix shipped in 2.10.7.
- 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 Bit integrations version
Enter the Bit integrations 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 “Bit integrations”, 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 “Bit integrations”.
- 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 (2.11.1). 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 Bit integrations vulnerabilities
Bit integrations <= 2.10.6 - Unauthenticated Privilege Escalation via Identity-Confused Log Re-execution to Account Takeover via Log Re-execution of Anonymous-Captured Field Data
Privilege escalation · CVE-2026-104749
Affected versions: ≤ 2.10.6
Fixed in: 2.10.7
Severity: High 7.5 · Disclosed Oct 13, 2026
Bit integrations <= 2.10.6 - Unauthenticated Stored Cross-Site Scripting via 'notification_content' Field via Public Bit Assist Webhook Callback
Cross-site scripting (XSS) · CVE-2026-102007
Affected versions: ≤ 2.10.6
Fixed in: 2.10.7
Severity: High 7.2 · Disclosed Oct 12, 2026
Bit integrations <= 2.9.0 - Unauthenticated Arbitrary File Read via Optional CF7 File Field
Arbitrary file read or deletion · CVE-2026-15006
Affected versions: ≤ 2.9.0
Fixed in: 2.9.1
Severity: High 7.5 · Disclosed Jul 31, 2026
Bit integrations <= 2.8.7 - Unauthenticated Server-Side Request Forgery via Form Field Upload Mapping
Server-side request forgery (SSRF) · CVE-2026-11989
Affected versions: ≤ 2.8.7
Fixed in: 2.8.8
Severity: Medium 6.5 · Disclosed Jun 18, 2026
Bit Integrations <= 2.4.10 - Open Redirect
Open redirect · CVE-2025-30884
Affected versions: ≤ 2.4.10
Fixed in: 2.5.0
Severity: High 7.2 · Disclosed Mar 27, 2025
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Bit integrations <= 2.10.6 - Unauthenticated Privilege Escalation via Identity-Confused Log Re-execution to Account Takeover via Log Re-execution of Anonymous-Captured Field DataPrivilege escalation · CVE-2026-104749 | ≤ 2.10.6 | 2.10.7 | High 7.5 | Oct 13, 2026 |
| Bit integrations <= 2.10.6 - Unauthenticated Stored Cross-Site Scripting via 'notification_content' Field via Public Bit Assist Webhook CallbackCross-site scripting (XSS) · CVE-2026-102007 | ≤ 2.10.6 | 2.10.7 | High 7.2 | Oct 12, 2026 |
| Bit integrations <= 2.9.0 - Unauthenticated Arbitrary File Read via Optional CF7 File FieldArbitrary file read or deletion · CVE-2026-15006 | ≤ 2.9.0 | 2.9.1 | High 7.5 | Jul 31, 2026 |
| Bit integrations <= 2.8.7 - Unauthenticated Server-Side Request Forgery via Form Field Upload MappingServer-side request forgery (SSRF) · CVE-2026-11989 | ≤ 2.8.7 | 2.8.8 | Medium 6.5 | Jun 18, 2026 |
| Bit Integrations <= 2.4.10 - Open RedirectOpen redirect · CVE-2025-30884 | ≤ 2.4.10 | 2.5.0 | High 7.2 | Mar 27, 2025 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 13, 2026.
Most common weaknesses in Bit integrations
Privilege escalation
1 issue
A user with a low-level account, such as a subscriber or customer, can give themselves administrator rights.
Cross-site scripting (XSS)
1 issue
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Arbitrary file read or deletion
1 issue
An attacker can read or delete files on the server. Deleting a configuration file can take the site offline, and reading one can expose passwords.
Frequently asked questions
Is Bit integrations safe to use?
Bit integrations is a well-known plugin with 20,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 (2.11.1) and turn on automatic updates.
How do I find which version of Bit integrations 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.
← All plugin vulnerabilitiesBit integrations on WordPress.org