CVE-2024-8760

Stackable – Page Builder Gutenberg Blocks <= 3.13.6 - Unauthenticated CSS Injection

2024-10-11 20:24
Francesco Carlucci

Strategic Overview

Status
Patched in 3.13.7
Affected Plugin
Stackable – Page Builder Gutenberg Blocks
Affected Version
<= 3.13.6
CVSS
5.3Medium
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2024-8760
View all Stackable – Page Builder Gutenberg Blocks vulnerabilities

At a glance

CVE-2024-8760 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Stackable WordPress plugin, affecting versions <= 3.13.6. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.13.7; sites on affected versions should update now. Disclosed October 2024, reported by Francesco Carlucci.

Vulnerability Overview

The Stackable – Page Builder Gutenberg Blocks plugin for WordPress is vulnerable to CSS Injection in all versions up to, and including, 3.13.6. This makes it possible for unauthenticated attackers to embed untrusted style information into comments resulting in a possibility of data exfiltration such as admin nonces with limited impact. These nonces could be used to perform CSRF attacks within a limited time window. The presence of other plugins may make additional nonces available, which may pose a risk in plugins that don't perform capability checks to protect AJAX actions or other actions reachable by lower-privileged users.

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 privileges on the target site, and no interaction from a victim user.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in Stackable <= 3.13.6 takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Stackable the fix is 3.13.7: builds <= 3.13.6 are affected, anything from 3.13.7 onward is not.

Remediation

Update to version 3.13.7, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Stackable 3.13.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2024-8760https://www.wordfence.com/threat-intel/vulnerabilities/id/1fd0b13c-7447-45da-9608-80b7629d9bbfhttps://nvd.nist.gov/vuln/detail/CVE-2024-8760

Related records

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