# CVE-2026-6089: WP CTA <= 2.1.2 - Authenticated (Administrator+) Server-Side Request Forgery

> Administrators can exploit SSRF in WP CTA plugin to access internal services and save responses as media attachments.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-7hj5-j6jm-q3vw

## What is CVE-2026-6089?

CVE-2026-6089 is a medium-severity server-side request forgery vulnerability in blendmedia WP CTA – Call Now Button, Sticky Button & Call to Action Builder, published on 29 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The WP CTA plugin for WordPress is vulnerable to Server-Side Request Forgery via the 'sticky_s_media' parameter in imported JSON files in all versions up to, and including, 2.1.2. This is due to the import_sidebars() function passing user-supplied URLs from imported JSON data to file_get_contents() with only FILTER_VALIDATE_URL validation (which allows internal IPs). This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application, which can be used to query and modify information from internal services. The response content is saved as a WordPress media attachment, making this a full-read SSRF.

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

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


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

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

## Is CVE-2026-6089 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6089 is a medium-severity server-side request forgery vulnerability in blendmedia WP CTA – Call Now Button, Sticky Button & Call to Action Builder, published on 29 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6089 in the wild and no public exploit code.

Affected product: blendmedia WP CTA – Call Now Button, Sticky Button & Call to Action Builder. 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-6089/ (Markdown: https://insights.sbomify.com/CVE-2026-6089/index.md)
```

## Sources

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

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