WordPress plugin · Updated daily · Source: Wordfence Intelligence

My Calendar vulnerabilities: affected versions and fixes

My Calendar has 20,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

My Calendar at a glance

  • 27 publicly disclosed vulnerabilities, 6 of them rated High or Critical. The most recent was disclosed on Nov 19, 2026.
  • Ranked #1195 by popularity on WordPress.org (20,000+ active installs).
  • The latest version is 3.8.14 (released Nov 15, 2026). The most recent security fix shipped in 3.8.14.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your My Calendar version

Enter the My Calendar version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “My Calendar”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “My Calendar”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (3.8.14). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known My Calendar vulnerabilities (latest 25 of 27)

  • My Calendar <= 3.8.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Event Title

    Cross-site scripting (XSS) · CVE-2026-119088

    Affected versions: ≤ 3.8.13

    Fixed in: 3.8.14

    Severity: Medium 6.4 · Disclosed Nov 19, 2026

  • My Calendar <= 3.8.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'event_post' Parameter

    Cross-site scripting (XSS) · CVE-2026-121538

    Affected versions: ≤ 3.8.13

    Fixed in: 3.8.14

    Severity: Medium 6.4 · Disclosed Nov 19, 2026

  • My Calendar <= 3.8.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'event_street' Address Field

    Cross-site scripting (XSS) · CVE-2026-120117

    Affected versions: ≤ 3.8.13

    Fixed in: 3.8.14

    Severity: Medium 6.4 · Disclosed Nov 19, 2026

  • My Calendar – Accessible Event Manager 3.8.8 - 3.8.11 - Unauthenticated Arbitrary Shortcode Execution

    Other weakness · CVE-2026-119714

    Affected versions: ≥ 3.8.8, < 3.8.11

    Fixed in: 3.8.11

    Severity: Medium 6.5 · Disclosed Oct 30, 2026

  • My Calendar <= 3.8.7 - Unauthenticated Privilege Escalation to 'mcs' Parameter via Reflected Shortcode Injection into 'above' Attribute

    Remote code execution · CVE-2026-104798

    Affected versions: ≥ 3.7, ≤ 3.7.17

    Fixed in: 3.4.25, 3.5.22, 3.6.18, 3.7.18, 3.8.8

    Severity: Critical 9.8 · Disclosed Oct 15, 2026

  • My Calendar <= 3.8.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'fallback' Shortcode Attribute

    Cross-site scripting (XSS) · CVE-2026-77186

    Affected versions: ≤ 3.8.3

    Fixed in: 3.8.4

    Severity: Medium 6.4 · Disclosed Sep 8, 2026

  • My Calendar <= 3.8.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'before' and 'after' Shortcode Attributes

    Cross-site scripting (XSS) · CVE-2026-77187

    Affected versions: ≤ 3.8.3

    Fixed in: 3.8.4

    Severity: Medium 6.4 · Disclosed Sep 8, 2026

  • My Calendar <= 3.7.8 - Unauthenticated SQL Injection via 'mc_auth' and 'mc_host' Parameters

    SQL injection · CVE-2026-6854

    Affected versions: ≤ 3.7.8

    Fixed in: 3.7.9

    Severity: High 7.5 · Disclosed Jul 7, 2026

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

    Missing authorization · CVE-2026-11896

    Affected versions: ≤ 3.7.14

    Fixed in: 3.7.15

    Severity: Medium 5.3 · Disclosed Jul 1, 2026

  • My Calendar <= 3.7.9 - Authenticated (Custom+) Missing Authorization to Unauthorized Event Publication via 'event_approved' Parameter

    Missing authorization · CVE-2026-7525

    Affected versions: ≤ 3.7.9

    Fixed in: 3.7.10

    Severity: Medium 4.3 · Disclosed May 13, 2026

  • My Calendar < 3.7.7 - Unauthenticated Denial of Service

    Missing authorization · CVE-2026-40308

    Affected versions: < 3.7.7

    Fixed in: 3.7.7

    Severity: Medium 5.3 · Disclosed Apr 16, 2026

  • My Calendar – Accessible Event Manager <= 3.7.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes

    Cross-site scripting (XSS) · CVE-2026-2355

    Affected versions: ≤ 3.7.3

    Fixed in: 3.7.4

    Severity: Medium 6.4 · Disclosed Mar 3, 2026

  • My Calendar <= 3.6.16 - Missing Authorization

    Missing authorization · CVE-2025-67592

    Affected versions: ≤ 3.6.16

    Fixed in: 3.6.17

    Severity: Medium 4.3 · Disclosed Dec 15, 2025

  • My Calendar <= 3.4.23 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

    Cross-site scripting (XSS) · CVE-2024-25916

    Affected versions: ≤ 3.4.23

    Fixed in: 3.4.24

    Severity: Medium 6.4 · Disclosed Feb 11, 2024

  • My Calendar <= 3.4.23 - Authenticated (Admin+) Stored Cross-Site Scripting via Events

    Cross-site scripting (XSS) · CVE-2024-1274

    Affected versions: ≤ 3.4.23

    Fixed in: 3.4.24

    Severity: Medium 4.4 · Disclosed Feb 11, 2024

  • My Calendar <= 3.4.21 - Unauthenticated SQL Injection

    SQL injection · CVE-2023-6360

    Affected versions: ≤ 3.4.21

    Fixed in: 3.4.22

    Severity: Critical 9.8 · Disclosed Nov 26, 2023

  • My Calendar <= 3.4.3 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2023-23813

    Affected versions: ≤ 3.4.3

    Fixed in: 3.4.4

    Severity: High 8.8 · Disclosed Jan 20, 2023

  • My Calendar <= 3.3.24.1 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2022-47427

    Affected versions: ≤ 3.3.24.1

    Fixed in: 3.3.25

    Severity: High 7.1 · Disclosed Jan 3, 2023

  • My Calendar <= 3.3.16 - Open Redirect

    Open redirect · CVE-2022-36371

    Affected versions: ≤ 3.3.16

    Fixed in: 3.3.17

    Severity: Medium 4.7 · Disclosed Aug 2, 2022

  • My Calendar <= 3.3.16 - Administrator+ Stored Cross-Site Scripting

    Cross-site scripting (XSS)

    Affected versions: ≤ 3.3.16

    Fixed in: 3.3.17

    Severity: Medium 5.5 · Disclosed Jul 18, 2022

  • My Calendar <= 3.2.17 - Subscriber+ Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2021-24927

    Affected versions: ≤ 3.2.17

    Fixed in: 3.2.18

    Severity: Medium 5.4 · Disclosed Nov 1, 2021

  • My Calendar <= 3.1.9 - Unauthenticated Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2019-15713

    Affected versions: ≤ 3.1.9

    Fixed in: 3.1.10

    Severity: Medium 6.1 · Disclosed Apr 30, 2019

  • My Calendar <= 2.5.16 - Authenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS)

    Affected versions: < 2.5.17

    Fixed in: 2.5.17

    Severity: Medium 6.4 · Disclosed Apr 4, 2018

  • My Calendar < 2.3.30 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS)

    Affected versions: < 2.3.30

    Fixed in: 2.3.30

    Severity: Medium 6.1 · Disclosed May 15, 2015

  • My Calendar <= 2.3.29 - Path Traversal to Remote Code Execution

    Remote code execution

    Affected versions: ≤ 2.3.29

    Fixed in: 2.3.30

    Severity: Critical 9.8 · Disclosed May 15, 2015

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 19, 2026.

Most common weaknesses in My Calendar

Cross-site scripting (XSS)

15 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

4 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Remote code execution

2 issues

An attacker can run code of their choice on your server. This is the most dangerous kind: it usually means a full takeover of the site.

Frequently asked questions

Is My Calendar safe to use?

My Calendar is a well-known plugin with 20,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.8.14) and turn on automatic updates.

How do I find which version of My Calendar my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesMy Calendar on WordPress.org