CVE-2023-6964

Gutenberg Blocks by Kadence Blocks – Page Builder Features <= 3.1.26 - Authenticated(Contributor+) Server-Side Request Forgery (SSRF)

2024-04-09 00:00
Lucio Sá

Strategic Overview

Status
Patched in 3.2.12
Affected Plugin
Kadence Blocks — Page Builder Toolkit for Gutenberg Editor
Affected Version
<= 3.1.26
CVSS
8.5High
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2023-6964
View all Kadence Blocks — Page Builder Toolkit for Gutenberg Editor vulnerabilities

At a glance

CVE-2023-6964 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Kadence Blocks WordPress plugin, affecting versions <= 3.1.26. It carries a CVSS score of 8.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.2.12; sites on affected versions should update now. Disclosed April 2024, reported by Lucio Sá.

Vulnerability Overview

The Gutenberg Blocks by Kadence Blocks – Page Builder Features plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.1.26 via the 'kadence_import_get_new_connection_data' AJAX action. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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)

Kadence Blocks <= 3.1.26 carries this weakness at kadence_import_get_new_connection_data, and reaching it takes an account at Contributor 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 Kadence Blocks the fix is 3.2.12: builds <= 3.1.26 are affected, anything from 3.2.12 onward is not.

Remediation

Update to version 3.2.12, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor 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: Kadence Blocks 3.2.12 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-6964https://www.wordfence.com/threat-intel/vulnerabilities/id/b01ad77f-2349-48bb-b4e9-f7cbce435de9https://nvd.nist.gov/vuln/detail/CVE-2023-6964

Related records

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