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

New CVE Detected

CVE-2026-78265 – Unauthenticated PHP Object Injection – The Events Calendar WordPress Plugin (≤ 6.17

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

Summary

CVE-2026-78265 is an unauthenticated PHP Object Injection (Deserialization of Untrusted Data, CWE-502) vulnerability in the "The Events Calendar" WordPress plugin, affecting versions up to and including 6.17.2. The flaw carries a CVSS v3.1 base score of 9.8 (Critical) and requires no authentication or user interaction to exploit over the network, making it a high-priority patching target for any internet-facing WordPress site running this plugin.

Technical details

  • Root cause: The plugin deserializes untrusted, attacker-supplied input without adequate validation, allowing insertion of arbitrary PHP objects (PHP Object Injection).
  • Trigger conditions: An unauthenticated attacker submits crafted serialized data to a vulnerable plugin entry point that is then passed to PHP’s deserialization functions.
  • Attack vector: Network-based, low attack complexity, no privileges or user interaction required.
  • Impact: Depending on other "gadget chains" available on the target (e.g., in the plugin’s legacy widget handling), successful exploitation can lead to arbitrary object instantiation, potentially escalating to remote code execution, data manipulation, or denial of service — reflected in the CVSS impact of high confidentiality, integrity, and availability loss.

Affected software

  • The Events Calendar (WordPress plugin) — versions up to and including 6.17.2
  • Fixed in version 6.17.3

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 version 6.17.3 or later, which hardens validation of copied legacy widget instances and addresses the deserialization issue.
  • If immediate patching is not possible:
    • Restrict or disable any public-facing endpoints/forms that accept widget or import-related input until patched.
    • Deploy a web application firewall (WAF) rule to block requests containing serialized PHP object payloads (e.g., strings beginning with O:, a:, s: in unexpected parameters).
    • Monitor logs for anomalous POST requests to plugin endpoints and for unexpected PHP errors referencing unserialize().
    • Take regular backups and verify site/database integrity given the potential for object injection to be chained into further compromise.

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