Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2024-11080 – Unauthenticated Hook Injection – Post Grid and Gutenberg Blocks – ComboBlocks (Word

Be the first to know when new zero-days emerge:

Summary

CVE-2024-11080 is a critical unauthenticated hook injection vulnerability (CWE-94, Improper Control of Generation of Code) in the "Post Grid and Gutenberg Blocks – ComboBlocks" WordPress plugin by pickplugins, affecting versions 2.2.85 through 2.3.32. The flaw resides in multiple functions within the plugin’s form-wrap component and allows unauthenticated attackers to trigger WordPress action hooks directly, without any prior security controls, authentication, or user interaction. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: Several functions in ~/includes/blocks/form-wrap/functions.php (identified at lines 116, 262, and 3249 of the plugin source) execute WordPress hooks based on unvalidated, attacker-supplied input, without verifying that the caller is authenticated or authorized.
  • Trigger conditions: An attacker can invoke the vulnerable form-wrap functionality remotely on any site running an affected version of the plugin, causing the plugin to fire arbitrary registered WordPress action hooks that the plugin (or other installed plugins/themes) exposes — no login, nonce, or special privileges are required.
  • Attack vector: Network-based (AV:N); low attack complexity (AC:L); no privileges required (PR:N); no user interaction (UI:N).
  • Impact: Because the impact depends on which hooks are registered on a given site, exploitation "grants" the attacker the ability to execute whatever actions those hooks perform — which, on sites with additional plugins registering sensitive hooks, can escalate to full confidentiality, integrity, and availability compromise, consistent with the CVSS impact subscores of C:H/I:H/A:H.

Affected software

  • Product: Post Grid and Gutenberg Blocks – ComboBlocks (WordPress plugin, vendor: pickplugins)
  • Versions: 2.2.85 up to and including 2.3.32

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Check the installed plugin version. As of this advisory’s publication, the latest publicly released version available via the WordPress.org plugin repository is 2.3.24 — still within the affected range (2.2.85–2.3.32) — so security teams should monitor the plugin’s official changelog and update to a patched release as soon as the vendor publishes one.
  • If no patch is available: Until a fixed version is released, consider deactivating or removing the "Post Grid and Gutenberg Blocks – ComboBlocks" plugin on internet-facing WordPress sites, or restrict/block external access to the plugin’s form-wrap endpoints at the web server or WAF layer.
  • General hardening: Audit installed WordPress plugins for unused or unnecessary hook-exposing functionality, and ensure a Web Application Firewall is in place to detect anomalous unauthenticated requests targeting plugin form-handling endpoints.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge