# CVE-2026-11989: Bit integrations <= 2.8.7 - Unauthenticated Server-Side Request Forgery via Form Field Upload Mapping

> Unauthenticated attackers can perform Server-Side Request Forgery to query and modify internal services via form field upload mapping in the Bit integrations plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-fxr5-h7mw-3fwm

## What is CVE-2026-11989?

CVE-2026-11989 is a medium-severity server-side request forgery vulnerability in bitpressadmin Bit integrations – Form Integration, Webhook, Spreadsheets, CRM, LMS & Email Automation, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-11989?


## How do I fix CVE-2026-11989?

No fix has been published for CVE-2026-11989 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11989 being exploited?

There is no known exploitation of CVE-2026-11989 in the wild and no public exploit code.

Public exploit code:

- My portfolio showcasing vulnerability research (CVE-2026-11989, CVE-2026-11395) and automated threat orchestration engineering (Lucius Engine, TalonVigil). (github_poc): https://github.com/repo-ranger21/security-portfolio-chris-peterson

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11989 and fix it if it is affected.

What it is: CVE-2026-11989 is a medium-severity server-side request forgery vulnerability in bitpressadmin Bit integrations – Form Integration, Webhook, Spreadsheets, CRM, LMS & Email Automation, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11989 in the wild and no public exploit code.

Affected product: bitpressadmin Bit integrations – Form Integration, Webhook, Spreadsheets, CRM, LMS & Email Automation. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-11989/ (Markdown: https://insights.sbomify.com/CVE-2026-11989/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11989
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11989
- OSV: https://osv.dev/vulnerability/CVE-2026-11989

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-11989/
Summaries are generated and may contain mistakes; the official description above is the record.