CVE-2024-11080

Post Grid and Gutenberg Blocks – ComboBlocks 2.2.85 - 2.3.32 - Unauthenticated Hook Injection

2026-09-04 19:52
Chloe Chamberland

Strategic Overview

Status
Patched in 2.3.33
Affected Plugin
Post Grid
Affected Version
2.2.85 – 2.3.32
CVSS
9.8Critical
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2024-11080
View all Post Grid vulnerabilities

At a glance

CVE-2024-11080 is a critical-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Post Grid WordPress plugin, affecting versions 2.2.85 – 2.3.32. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.3.33; sites on affected versions should update now. Disclosed September 2026, reported by Chloe Chamberland.

Vulnerability Overview

The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress is vulnerable to Unauthenticated Hook Injection in versions 2.2.32 to 2.3.1 via several functions in the ~/includes/blocks/form-wrap/function.php file. This makes it possible for unauthenticated attackers to execute actions with hooks in WordPress, granted no other security controls are present in the function.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in Post Grid 2.2.85 – 2.3.32 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 Post Grid the fix is 2.3.33: builds 2.2.85 – 2.3.32 are affected, anything from 2.3.33 onward is not.

Remediation

Update to version 2.3.33, 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: Post Grid 2.3.33 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-11080https://www.wordfence.com/threat-intel/vulnerabilities/id/ec8666d4-042e-4cf4-86f5-474a69d90ff6https://nvd.nist.gov/vuln/detail/CVE-2024-11080

Related records

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