WordPress security changelog
MEDIUM CVE-2026-1857 Deferred

Gutenberg Blocks with AI by Kadence WP: Server-side request forgery

Gutenberg Blocks with AI by Kadence WP is affected by server-side request forgery. Exploitation requires at least contributor-level access. The vulnerable server can be induced to make attacker-selected network requests.

CVE / CNA score 4.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Gutenberg Blocks with AI by Kadence WP
Plugin slug
kadence-blocks
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Feb 18, 2026
Weakness
CWE-918 — Server-Side Request Forgery (SSRF)

This CVE was published Feb 18, 2026 and is one of 17 known issues for this plugin.

Update, patch or deactivate.

Update Gutenberg Blocks with AI by Kadence WP to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The Gutenberg Blocks with AI by Kadence WP plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.6.1. This is due to insufficient validation of the `endpoint` parameter in the `get_items()` function of the GetResponse REST API handler. The endpoint's permission check only requires `edit_posts` capability (Contributor role) rather than `manage_options` (Administrator). This makes it possible for authenticated attackers, with Contributor-level access and above, to make server-side requests to arbitrary endpoints on the configured GetResponse API server, retrieving sensitive data such as contacts, campaigns, and mailing lists using the site's stored API credentials. The stored API key is also leaked in the request headers.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Primary and upstream sources