dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-11896

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The My Calendar WordPress plugin fails to validate the 'vcal' parameter before using it to retrieve calendar event data, allowing unauthenticated attackers to access non-public event information through direct object reference. Attackers can enumerate occurrence IDs to export iCalendar data from draft, trashed, or personal events, exposing titles, descriptions, dates, locations, organizer details, and permalinks.

MitigationImplement proper authorization checks and input validation on the vcal parameter to ensure users can only export iCalendar data for events they have permission to view. Consider requiring authentication for sensitive event exports and adding rate limiting to prevent enumeration attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm My Calendar plugin is installed
    Navigate to WordPress Admin > Plugins and verify 'My Calendar' is listed as an active plugin, or check the /wp-content/plugins/my-calendar/ directory exists and contains the plugin files
    Affected if My Calendar plugin is installed and active
  2. Identify the installed My Calendar version
    In WordPress Admin, go to Plugins > My Calendar > View Details, or inspect the main plugin file (my-calendar.php) to find the 'Version' header comment
    Affected if The installed version has not yet received the fix for CVE-2026-11896 (compare your version to the patched release)
  3. Verify vcal endpoint is accessible to unauthenticated users
    Open a browser or use curl to request: https://your-site.com/?vcal=1 (without logging in)
    Affected if The request returns iCalendar data without requiring authentication
  4. Test if non-public events can be exported
    Using the vcal parameter with different occurrence IDs (e.g., ?vcal=1, ?vcal=2, etc.), attempt to retrieve data for events that are draft, trashed, or marked as personal/private
    Affected if Non-public events (draft, trashed, private) are accessible via the vcal parameter without authentication

Your environment is affected if My Calendar is installed AND the vcal endpoint returns event data without authentication, exposing draft, trashed, or personal events to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks and input validation on the vcal parameter to ensure users can only export iCalendar data for events they have permission to view. Consider requiring authentication for sensitive event exports and adding rate limiting to prevent enumeration attacks.

Recommended fix High confidence

My Calendar 3.7.15 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'My Calendar – Accessible Event Manager' in the plugin list
  4. Check if the current version is 3.7.14 or earlier
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/my-calendar and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the plugin version shows 3.7.15 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11896 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11896 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data