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.
Published: 2026-09-12
Score: 9.8 Critical
EPSS: < 1% Very Low
KEV: No
Impact: Remote Code Execution
Action: Immediate Patch
AI Analysis

Impact

The Events Calendar plugin is vulnerable to PHP object injection that allows unauthenticated attackers to execute arbitrary code on the server. The flaw lies in the is_safe_widget_instance function, which lacks proper protection and can be bypassed because PHP’s magic methods are invoked before unserialize() runs. An attacker can supply a crafted payload that is processed during event rendering, enabling code execution with the web host’s permissions. This exploitation does not require any authentication or administrative approval and can be performed solely by submitting a malicious comment or request.

Affected Systems

WordPress sites that have installed The Events Calendar by StellarWP up to and including version 6.17.4 are affected. The vulnerability exists in all code paths that invoke is_safe_widget_instance when rendering events. Sites that have comments enabled and visible on event pages create the specific pathway that attackers can abuse.

Risk and Exploitability

The CVSS score of 9.8 marks this flaw as critical, while the EPSS score of less than 1% indicates it has not been widely exploited yet. The CVE is not listed in the CISA KEV catalog, so active exploits are not documented. Attackers can send a crafted comment or visitor request that includes the malicious serialized payload; because the plugin processes comment HTML via do_blocks() during rendering, the payload is executed before any moderation. The exploit therefore requires no special privileges beyond the ability to post a comment on an event page.

Generated by OpenCVE AI on September 12, 2026 at 15:51 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Events Calendar plugin to the latest version (6.18 or newer) where the deserialization logic has been hardened.
  • If an immediate upgrade is not possible, disable comments on event pages so that the exploitation vector that relies on visitor comments is removed.
  • As a temporary measure, remove the plugin from the site or replace it with an alternative event management solution until a proper patch is applied.

Generated by OpenCVE AI on September 12, 2026 at 15:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 12 Sep 2026 07:45:00 +0000

Type Values Removed Values Added
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.
Title The Events Calendar <= 6.17.4 - Unauthenticated PHP Object Injection to Remote Code Execution
Weaknesses CWE-502
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-09-12T07:39:15.165Z

Reserved: 2026-08-21T21:25:40.295Z

Link: CVE-2026-78006

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-12T08:16:24.240

Modified: 2026-09-12T08:16:24.240

Link: CVE-2026-78006

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-12T16:00:14Z

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data