CVE Tools

CVE-2026-78006

The Events Calendar <= 6.17.4 - Unauthenticated PHP Object Injection to Remote Code Execution

Published: Sep 12, 2026Updated: Sep 14, 2026 Sources: CVE List NVDCWE-502

Description

The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.4 via the is_safe_widget_instance function. This is due to insufficient protection in is_safe_widget_instance, which can be bypassed because PHP fires magic methods during its pre-parse, combined with enable_rendering_widget_copied() forging a valid wp_hash integrity attribute before unserialize() is reached. This makes it possible for unauthenticated attackers to execute code on the server. This is exploitable without authentication or approval because the plugin's V2 single-event template runs do_blocks() over buffered comment HTML, and WordPress returns a moderation-hash URL that allows an unauthenticated commenter to immediately view their own pending comment, delivering the injected block markup to the vulnerable code path before any moderation occurs. This does require comments to be enabled and visible on events.

In plain language

AI Act now

The Events Calendar (up to 6.17.4) has a critical bug where anyone on the internet can post a crafted comment on an event and run harmful code on the server—this is a serious risk if you have event comments enabled.

Executive summary

Unauthenticated PHP Object Injection leading to Remote Code Execution exists in The Events Calendar up to and including 6.17.4; an attacker bypasses input-safety handling in a PHP path (is_safe_widget_instance) when comments are processed/rendered, enabling server-side command execution without login if event comments are enabled and reachable.

If affected, business impact
Full website takeoverServer compromiseCustomer data exposureOperations disruption

What to do now

  1. Check whether your WordPress site uses “The Events Calendar” version 6.17.4 or earlier.
  2. Check whether event comments are enabled and visible on events (people can post/view comments on event pages).
  3. If both are true, disable or restrict comments on event pages immediately (at least temporarily) to remove the attacker entry point.
  4. Look for an official fixed update from the plugin vendor for The Events Calendar; apply it as soon as it’s available.
  5. If you cannot update right away, keep event comments disabled and block public posting to reduce exposure until a fixed version is released and applied.
May need vendor / contractor work

CVSS Vector Breakdown

AV:NAC:LPR:NUI:NS:UC:HI:HA:H
Exploitability
AV:NAttack Vector
Network
AC:LAttack Complexity
Low
PR:NPrivileges Required
None
UI:NUser Interaction
None
Scope
S:UScope
Unchanged
Impact
C:HConfidentiality
High
I:HIntegrity
High
A:HAvailability
High

Weaknesses

Affected Products

Exploitability

No known exploits, KEV entries, or remediation guidance available for this vulnerability yet.

Attack Graph

Products CVE Techniques Tactics

Click technique nodes for MITRE ATT&CK details · drag to pan · Ctrl/ + scroll to zoom, or go fullscreen.

MITRE ATT&CK

3 techniques
Execution
Initial Access
View detailed technique mapping

References

and 4 more references View all →
2

Unlock Complete Vulnerability Intelligence

Get the full picture for CVE-2026-78006 and every CVE in our database. Create a free account — no credit card required.

Create Free Account
Plain-language analysis
Impact assessment and exploitation scenario in plain English
Attack graph visualization
Interactive attack path and kill chain mapping
Exploit details & PoC links
ExploitDB, Metasploit, GitHub PoCs with direct links
Nuclei scanner templates
Ready-to-use vulnerability scanner templates
Full remediation guide
Patch instructions, workarounds, and compliance impact
Interactive AI chat
Ask questions about this vulnerability in natural language
Related vulnerabilities
Semantically similar CVEs and attack patterns
REST API & MCP access
Integrate vulnerability data into your workflows