CVE-2026-6089

WP CTA <= 2.1.2 - Authenticated (Administrator+) Server-Side Request Forgery

2026-07-28 21:18
Nguyen Quang Truong

Strategic Overview

Status
Patched in 2.1.3
Affected Plugin
WP CTA – Call Now Button, Sticky Button & Call to Action Builder
Affected Version
2.1.2
CVSS
4.9Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2026-6089
View all WP CTA – Call Now Button, Sticky Button & Call to Action Builder vulnerabilities

At a glance

CVE-2026-6089 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the WP CTA WordPress plugin, affecting versions 2.1.2. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 2.1.3; sites on affected versions should update now. Disclosed July 2026, reported by Nguyen Quang Truong.

Vulnerability Overview

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.

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 interaction from a victim user. A successful exploit has high impact on confidentiality.

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

WP CTA 2.1.2 carries this weakness at sticky_s_media, and reaching it takes an account at Administrator level or above. 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 WP CTA the fix is 2.1.3: builds 2.1.2 are affected, anything from 2.1.3 onward is not.

Remediation

Update to version 2.1.3, or a newer patched version

How does WordSec protect against this?

An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP CTA 2.1.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-6089https://www.wordfence.com/threat-intel/vulnerabilities/id/df5fc86f-e4ba-424b-bece-79abd763cf74https://nvd.nist.gov/vuln/detail/CVE-2026-6089

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C