CVE-2026-11896

My Calendar <= 3.7.14 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Disclosure via 'vcal' Parameter

2026-07-01 20:04
Athiwat Tiprasaharn (Jitlada)

Strategic Overview

Status
Patched in 3.7.15
Affected Plugin
My Calendar – Accessible Event Manager
Affected Version
<= 3.7.14
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-11896
View all My Calendar – Accessible Event Manager vulnerabilities

At a glance

CVE-2026-11896 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the My Calendar WordPress plugin, affecting versions <= 3.7.14. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.7.15; sites on affected versions should update now. Disclosed July 2026, reported by Athiwat Tiprasaharn (Jitlada).

Vulnerability Overview

The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.7.14 via the 'vcal' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to enumerate occurrence IDs and access the full iCalendar export of non-public, draft, trashed, and personal calendar events, disclosing sensitive event metadata including titles, descriptions, dates, locations, organizer and host details, permalinks, and related calendar metadata.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

My Calendar <= 3.7.14 carries this weakness at vcal, and reaching it takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For My Calendar the fix is 3.7.15: builds <= 3.7.14 are affected, anything from 3.7.15 onward is not.

Remediation

Update to version 3.7.15, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: My Calendar 3.7.15 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-11896https://www.wordfence.com/threat-intel/vulnerabilities/id/a72639df-fa05-414c-b30c-eb285f59d945https://nvd.nist.gov/vuln/detail/CVE-2026-11896

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C