CVE-2024-11080: The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress is vulnerable to Unauthenticated Hook Injection in vulnerability
CVE-2024-11080 affects The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress is vulnerable to Unauthenticated Hook Injection in 2.2.32 to 2.3.1 via The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress. The published...
What happened
A security weakness in The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress is vulnerable to Unauthenticated Hook Injection in is being tracked as CVE-2024-11080. CVE-2024-11080 affects The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress is vulnerable to Unauthenticated Hook Injection in 2 2 32 to 2 3 1 via The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress.
The available description indicates that the vulnerable path can be reached remotely or from an untrusted network, so the exposure of The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress is vulnerable to Unauthenticated Hook Injection in becomes part of the attack condition. The available advisory information identifies 2 2 32 to 2 3 1 via The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress as affected versions. CVE-2024-11080 currently carries a CRITICAL 9 8 severity signal in the retained vulnerability data.
This makes it possible for unauthenticated attackers to execute actions with hooks in WordPress, granted no other security controls are present in the function. The published description indicates a remote or untrusted-network exploitation path. 1 via several functions in the ~/includes/blocks/form-wrap/function.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
1 via several functions in the ~/includes/blocks/form-wrap/function.
This makes it possible for unauthenticated attackers to execute actions with hooks in WordPress, granted no other security controls are present in the function.
CVE-2024-11080 currently carries a CRITICAL 9.8 severity signal in the retained vulnerability data.
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.
A security weakness in The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress is vulnerable to Unauthenticated Hook Injection in is being tracked as CVE-2024-11080. The available advisory information identifies 2.2.32 to 2.3.1 via The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress as affected versions. The available description indicates that the vulnerable path can be reached remotely or from an untrusted network, so the exposure of The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress is vulnerable to Unauthenticated Hook Injection in becomes part of the attack condition. This makes it possible for unauthenticated attackers to execute actions with hooks in WordPress, granted no other security controls are present in the function. The issue currently carries a CRITICAL 9.8 severity signal in the available reporting. There is no reported exploitation in the current available reporting, so the public picture at this point is a disclosed vulnerability with known exploitation conditions rather than a confirmed compromise of every affected installation.
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below shows how the vulnerability can be reached and what successful exploitation can produce. Each stage is labeled by evidence status.
Required condition: an affected The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress is vulnerable to Unauthenticated Hook Injection in 2.2.32 to 2.3.1 via The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress instance is reachable from a network position available to the attacker.
attacker-controlled network input reaches the vulnerable function on the affected The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress is vulnerable to Unauthenticated Hook Injection in service.
Not publicly disclosed in enough technical detail to describe the mechanism without inference.
Not publicly disclosed in enough detail to state a specific post-exploitation result without inference.
Identify remotely reachable The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress is vulnerable to Unauthenticated Hook Injection in 2.2.32 to 2.3.1 via The Post Grid and Gutenberg Blocks – ComboBlocks plugin for WordPress; remove unnecessary exposure; apply the vendor fix or mitigation; then review service, network and identity telemetry for exploitation attempts or unexpected follow-on activity.
Why this matters to you
CVE-2024-11080 matters because the practical risk is not the score alone — it is whether the affected technology or service exists in your environment and whether the reported trigger or exposure path can reach it. The current severity is CRITICAL 9.8. No exploitation flag is currently present in the CDF data, but that does not remove the need to validate affected systems.
Does this deserve attention in my environment?
Check the conditions below against your use of the affected technology or service.
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Search endpoint, software and asset inventory for the affected technology or service.
- Confirm the vendor-recommended fixed version or mitigation and verify deployment, not just assignment, across affected assets.
- Review relevant endpoint, application, network or identity telemetry for activity associated with exploitation of the affected component.
- Track vendor and government guidance for any change in exploitation status while remediation is underway.
What remains unconfirmed
- Available reporting does not currently indicate exploitation, but that can change as vendor, government or threat-intelligence reporting develops.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.