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

New CVE Detected

CVE-2026-78006 – Unauthenticated RCE via PHP Object Injection – The Events Calendar (WordPress) ≤ 6.

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

Summary

CVE-2026-78006 is a critical unauthenticated Remote Code Execution vulnerability in the "The Events Calendar" WordPress plugin, caused by insufficient validation in the is_safe_widget_instance function that allows attacker-controlled data to reach an unsafe PHP deserialization (unserialize()) call. The flaw is rated CVSS 9.8 (Critical) and can be triggered by an unauthenticated visitor, making any exposed WordPress site running the plugin with comments enabled on events a high-risk target.

Technical details

  • Root cause: is_safe_widget_instance is meant to verify that a copied legacy widget instance is safe before it is processed, but the check can be bypassed because PHP invokes magic methods during pre-parsing, and the plugin’s enable_rendering_widget_copied() routine forges a valid wp_hash integrity attribute before the data reaches unserialize().
  • Trigger conditions: The target site must have comments enabled and visible on events. The plugin’s V2 single-event template runs do_blocks() over buffered comment HTML, and WordPress issues a moderation-hash URL that lets an unauthenticated commenter immediately view their own pending (not-yet-moderated) comment — delivering attacker-crafted block markup to the vulnerable code path before any moderation review occurs.
  • Attack vector: Network, no authentication or user interaction required (an attacker only needs to submit a comment on a public event page).
  • Impact: Successful exploitation allows PHP Object Injection that can be leveraged into arbitrary code execution on the server, with full loss of confidentiality, integrity, and availability.

Affected software

  • Product: The Events Calendar (StellarWP), WordPress plugin
  • Vulnerable versions: All versions up to and including 6.17.4

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: Update The Events Calendar plugin to the latest available version. A security release addressing hardened validation of copied widget instances was published after 6.17.4; ensure the installed version is not on the affected 6.17.4-and-earlier line.
  • If patching is not immediately possible:
    • Disable comments on events (tribe_events post type) to remove the delivery path for the malicious block markup.
    • Consider deploying a Web Application Firewall rule to block malformed/serialized PHP payloads submitted through comment fields.
    • Audit existing comments and post content for injected wp:legacy-widget block markup and remove any suspicious entries.

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