Two critical, unauthenticated vulnerability chains in The Events Calendar WordPress plugin could let remote attackers reset administrator passwords, execute operating-system commands, and take over vulnerable websites.
The vulnerabilities affect The Events Calendar, a widely used WordPress plugin installed on more than 600,000 sites. StellarWP, the plugin’s developer, has released fixes, and administrators are urged to update to version 6.17.4.1 immediately.
The vulnerabilities, tracked as CVE-2026-78006 and CVE-2026-78159, each carry a CVSS severity score of 9.8 out of 10.
Critical WordPress Plugin Bugs
CVE-2026-78006 affects plugin versions up to and including 6.17.4 and enables unauthenticated PHP object injection that can lead to remote code execution.
Attackers can abuse unsafe deserialization behavior to trigger a gadget chain within the plugin and execute arbitrary commands on the underlying web server.
The second flaw, CVE-2026-78159, affects versions up to and including 6.17.3. It stems from inadequate validation of a widget classes map and can enable arbitrary PHP callable invocation.
Rather than directly executing a system command, attackers can invoke WordPress functions with attacker-controlled arguments.
Researchers demonstrated that this route could be used to invoke the wp_update_user() function and reset the password for administrator account ID 1.
Once logged in as an administrator, an attacker could upload a malicious plugin, establish persistent access, steal data, or deploy malware.
Both attack chains originate in the plugin’s V2 single-event rendering process. The Events Calendar captures the rendered event page, including its comment area, and passes the resulting HTML to WordPress’s do_blocks() function.
Normally, WordPress processes Gutenberg blocks in post content rather than untrusted comment text. However, the plugin’s approach expands block parsing to comments submitted on event pages.
WordPress comment sanitization preserves HTML comment delimiters, allowing crafted Gutenberg block markup to survive and reach the vulnerable widget-rendering pipeline.
Exploitation requires comments to be enabled on event posts and the plugin’s “Show comments on event pages” setting to be active. Importantly, an attacker does not need a WordPress account, approved comment, or administrator interaction.
After submitting a malicious comment, an attacker can use WordPress’s pending-comment preview mechanism, which provides the commenter with a moderation-hash URL. Loading that URL can cause the crafted block content to be processed before a moderator approves the comment.
Mitigation
Chloe Chamberland acknowledged the disclosures on August 24. StellarWP released an initial fix for the object-injection issue on August 25, and a fully patched release addressing the vulnerability chains became available in version 6.17.4.1.
Wordfence Premium, Care, and Response users received firewall protection for known exploit attempts on August 22. Free Wordfence users are scheduled to receive the same rule on September 21.
Site owners should immediately update The Events Calendar to version 6.17.4.1 or later. Administrators should also review event-page comment settings, inspect administrator accounts and installed plugins for unauthorized changes, and monitor web-server logs.
Join 16,000+ SOC teams using ANY.RUN to streamline threat investigations and reduce manual effort. Explore for your team