ZeroHour
Cyber Security Newspublished ()ingested Abinaya
Part of a story covered by 2 sources: “Critical WordPress Plugin Flaws Put Over 600,000 Websites at Risk of Takeover” — merged summary and timeline →

Critical WordPress Plugin Flaws Put Over 600,000 Websites at Risk of Takeover

AI summary · glm-5.3

Two CVSS 9.8 flaws in The Events Calendar WordPress plugin expose 600,000+ sites to unauthenticated RCE and admin takeover.

Wordfence Argus discovered CVE-2026-78006 and CVE-2026-78159 (both CVSS 9.8) in StellarWP's The Events Calendar plugin, affecting over 600,000 active installations. CVE-2026-78006 exploits PHP object injection via crafted pending comments to execute OS commands; CVE-2026-78159 abuses a specially prepared array to call WordPress functions, enabling admin password resets and subsequent RCE. Both flaws are unauthenticated and patched in version 6.17.4.1, released after reports on August 21-22, 2026.

  • CVE-2026-78006 and CVE-2026-78159 both scored CVSS 9.8, exploitable without authentication
  • Over 600,000 active installations of The Events Calendar affected
  • First chain abuses PHP object injection via pending comment preview; second enables admin password reset
  • Patch available in version 6.17.4.1; Wordfence firewall rules shipped August 22
  • No confirmed in-the-wild exploitation reported

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2026-78006
+1 in the same advisory: …78159
Unauthenticated RCE in The Events Calendar WordPress Plugin

The Events Calendar WordPress plugin is vulnerable to unauthenticated remote code execution (CWE-502, unsafe deserialization) in all versions up to and including 6.17.4 via the is_safe_widget_instance function, whose protection can be bypassed because PHP fires magic methods during pre-parse while enable_rendering_widget_copied() forges a valid wp_hash integrity attribute before unserialize() is reached. The flaw is reachable 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 lets an unauthenticated commenter immediately view their own still-pending comment, delivering attacker-injected block markup to the vulnerable code path before moderation occurs. Successful exploitation gives an unauthenticated attacker arbitrary code execution on the web server with full confidentiality, integrity, and availability impact. Any site running a vulnerable version is affected, but only when comments are enabled and visible on events. No public proof-of-concept is known, the issue is not in CISA's KEV catalog, and no in-the-wild exploitation has been confirmed.

Do: Update The Events Calendar to the latest available release (any version newer than 6.17.4) as soon as possible. Until patched, disable comments on events or prevent them from being publicly visible, since exploitation requires comments to be enabled and viewable on event pages. Review logs for pending comments submitted to events and unexpected widget/serialized data, and treat comment moderation queues on event posts with suspicion.

9.8<1% PoC ×2
  • StellarWP (The Events Calendar) The Events Calendar WordPress plugin All versions up to and including 6.17.4
mass≈200,000+ sites (plugin reports 200,000+ active installs on WordPress.org), with the exploitable subset smaller because comments must be enabled and visible on…
Full article573 words · extracted from cybersecuritynews.com · click to collapse

Two critical vulnerabilities in The Events Calendar WordPress plugin could allow unauthenticated attackers to take over vulnerable websites.

The flaws affect more than 600,000 active installations. They can lead to remote code execution, administrator password resets, malware deployment, and full server compromise.

Wordfence Argus, developed by the Wordfence Threat Intelligence team, discovered the two independent vulnerability chains on August 21 and August 22, 2026.

Both issues exist in the plugin’s widget-rendering process. They can be exploited without requiring a login, account registration, or user interaction.

The affected plugin is The Events Calendar, developed by StellarWP. Website administrators are strongly advised to update to version 6.17.4.1 or later immediately.

Critical WordPress Plugin Flaws

The first issue, tracked as CVE-2026-78006, has a CVSS score of 9.8. It affects The Events Calendar versions up to 6.17.4. The vulnerability lets attackers abuse PHP object injection to execute operating system commands on the affected web server.

The attack starts when a malicious user submits a specially crafted comment to an event page. The attack only works when comments are enabled for event pages and the plugin’s “Show comments on event pages” setting is active.

However, the attacker doesn’t need an approved comment because WordPress lets comment authors preview their own pending comments through a moderation link.

The Events Calendar processes the full event page, including comments, as Gutenberg blocks. This unsafe design allows malicious block content placed inside a pending comment to reach the plugin’s widget-rendering code.

The vulnerable code validates a widget instance before generating a trusted WordPress hash for it. Researchers found that a malformed serialized PHP payload can bypass the validation. Although the plugin attempts to block dangerous objects, PHP may trigger magic methods while processing the attacker-controlled data.

This behavior can lead to command execution through a vulnerable deserialization routine. An attacker could run commands with the web server user’s permissions, potentially allowing data theft, website defacement, malware installation, or lateral movement within the hosting environment.

The second flaw, CVE-2026-78159, also carries a CVSS score of 9.8. It affects versions up to 6.17.3 and uses a separate path to gain control of the site.

Instead of using object injection, the second attack uses a specially prepared array that passes the plugin’s safety check. The attacker-controlled data is then passed into the widget template system, where it can reach a function that accepts callable PHP functions.

Researchers found that an attacker could abuse this behavior to call WordPress functions with attacker-supplied arguments. One demonstrated impact is resetting the site administrator’s password. The attacker could then sign in as an administrator, upload a malicious plugin, and obtain remote code execution.

StellarWP received the vulnerability reports through the Wordfence Vulnerability Management Portal. The vendor acknowledged both reports on August 24, 2026, and released patches shortly afterward. The fully patched release is version 6.17.4.1.

Wordfence Premium, Care, and Response customers received firewall protection for known exploit attempts on August 22, 2026. Free Wordfence users are scheduled to receive the same rule on September 21, 2026.

Site owners should update The Events Calendar immediately, review whether comments are enabled on event pages, remove unneeded plugins, and inspect administrator accounts and server logs for suspicious activity.

Learn 7 Metric-Gated AI SOC Deployment Phases – Download Free AI SOC Deployment Playbook 2026.

Abinayahttps://cybersecuritynews.com/

Abi is a Security Editor and fellow reporter with Cyber Security News. She is covering various cyber security incidents happening in the Cyber Space.

Text extracted automatically; images, tables and formatting may be missing. Original: https://cybersecuritynews.com/critical-wordpress-plugin-flaws/