Bit integrations <= 2.8.7 - Unauthenticated Server-Side Request Forgery via Form Field Upload Mapping
Strategic Overview
- Status
- Patched in 2.8.8
- Affected Plugin
- Bit integrations – Form Integration, Webhook, Spreadsheets, CRM, LMS & Email Automation
- Affected Version
<= 2.8.7- CVSS
- 6.5Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2026-11989
At a glance
CVE-2026-11989 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Bit integrations WordPress plugin, affecting versions <= 2.8.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.8.8; sites on affected versions should update now. Disclosed June 2026, reported by Lucius-log.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in Bit integrations <= 2.8.7 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Bit integrations the fix is 2.8.8: builds <= 2.8.7 are affected, anything from 2.8.8 onward is not.
Remediation
Update to version 2.8.8, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Bit integrations 2.8.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Bit integrations – Form Integration, Webhook, Spreadsheets, CRM, LMS & Email Automation
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C