dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-11989

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
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 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 confidence

This is an unauthenticated SSRF vulnerability in the Bit integrations WordPress plugin's upload_attachment function. Attackers can make arbitrary web requests from the server by exploiting form integrations configured with WooCommerce product image, gallery, downloadable files, or Google Contacts attachment fields—a default configuration use case.

MitigationUpdate the plugin to version 2.8.8 or later. If no patch is available, disable form integrations using WooCommerce or Google Contacts attachments, or temporarily disable the plugin until a fix is released.

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WordPress installation
    Check for wp-config.php in the web root directory or look for WordPress-specific HTML comments in page source
    Affected if Not a WordPress site - vulnerability does not apply
  2. Locate Bit integrations plugin
    Check wp-content/plugins/ directory for 'bit-integrations' folder, or query the WordPress plugins API endpoint /wp-json/wp/v2/plugins?search=bit-integrations
    Affected if Plugin not installed - vulnerability does not apply
  3. Check installed plugin version
    Access WordPress admin > Plugins > Installed Plugins > Bit integrations, or read the 'Version:' line from the plugin's main PHP file header in wp-content/plugins/bit-integrations/readme.txt
    Affected if Version is present and less than 2.8.8 - may be vulnerable
  4. Identify form integrations with WooCommerce attachments
    Navigate to Bit integrations plugin settings in WordPress admin. Look for form integrations configured with WooCommerce product image, gallery, or downloadable files attachment fields under the WooCommerce integration section
    Affected if Form integrations are configured with WooCommerce product image, gallery, or downloadable files attachments - exploitation path exists
  5. Identify form integrations with Google Contacts attachments
    Navigate to Bit integrations plugin settings. Look for form integrations configured with Google Contacts attachment fields under the Google Contacts integration section
    Affected if Form integrations are configured with Google Contacts attachments - exploitation path exists

User is affected if the Bit integrations plugin is installed with version less than 2.8.8 AND has active form integrations using WooCommerce product image, gallery, downloadable files, or Google Contacts attachment fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 2.8.8 or later. If no patch is available, disable form integrations using WooCommerce or Google Contacts attachments, or temporarily disable the plugin until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11989 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11989 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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