HomeWordPress vulnerabilitiesBit integrations
Bit integrations vulnerabilities
Bit integrations has 2 known vulnerabilities in this database. The most recent published record is dated 1 Aug 2026.
- Known vulnerabilities
- 2
- Active installs
- 20,000+
- Latest version
- 2.10.6
- Last updated
- 27 Sep 2026
- Most recent
- 1 Aug 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 |
|---|---|---|---|---|
| Path traversal CVE-2026-15006 | High 7.5 | Up to 2.9.0 | Fixed in a later version (latest 2.10.6) | 1 Aug 2026 |
| Server-side request forgery (SSRF) CVE-2026-11989 | Medium 6.5 | Up to 2.8.7 | Fixed in a later version (latest 2.10.6) | 19 Jun 2026 |
Read the published descriptions
- CVE-2026-15006, 1 Aug 2026
- The Bit integrations - Form Integration, Webhook, Spreadsheets, CRM, LMS & Email Automation plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.9.0 via the processAttachment function. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. CVE record
- CVE-2026-11989, 19 Jun 2026
- The Bit integrations - Form Integration, Webhook, Spreadsheets, CRM, LMS & Email Automation plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.8.7 via the upload_attachment. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. Exploitation requires a form integration to be configured with a field mapped to a WooCommerce product image, product gallery, downloadable files, or Google Contacts attachment field, which is a default use case for these integrations. CVE record
What to do if you run Bit integrations
If you run Bit integrations, 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 Bit integrations vulnerabilities
Free. We email you when a new vulnerability is published for Bit integrations, 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.