HomeWordPress vulnerabilitiesMy Calendar
My Calendar vulnerabilities
My Calendar has 17 known vulnerabilities in this database. The most recent published record is dated 20 Nov 2026.
- Known vulnerabilities
- 17
- Active installs
- 20,000+
- Latest version
- 3.8.13
- Last updated
- 5 Nov 2026
- Most recent
- 20 Nov 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-120117 | Medium 6.4 | Up to 3.8.13 | No fixed version yet | 2 d ago |
| Cross-site scripting (XSS) CVE-2026-118055 | Medium 6.4 | Up to 3.8.13 | No fixed version yet | 2 d ago |
| Cross-site scripting (XSS) CVE-2026-119088 | Medium 6.4 | Up to 3.8.13 | No fixed version yet | 2 d ago |
| Cross-site scripting (XSS) CVE-2026-121538 | Medium 6.4 | Up to 3.8.13 | No fixed version yet | 2 d ago |
| Remote code execution CVE-2026-119714 | Medium 6.5 | Before 3.8.11 | Fixed in 3.8.11 | 30 Oct 2026 |
| Remote code execution CVE-2026-104798 | Critical 9.8 | Up to 3.8.7 | Fixed in a later version (latest 3.8.13) | 16 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-77187 | Medium 6.4 | Up to 3.8.3 | Fixed in a later version (latest 3.8.13) | 9 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-77186 | Medium 6.4 | Up to 3.8.3 | Fixed in a later version (latest 3.8.13) | 9 Sep 2026 |
| SQL injection CVE-2026-6854 | High 7.5 | Up to 3.7.8 | Fixed in a later version (latest 3.8.13) | 8 Jul 2026 |
| Broken access control CVE-2026-11896 | Medium 5.3 | Up to 3.7.14 | Fixed in a later version (latest 3.8.13) | 2 Jul 2026 |
| Broken access control CVE-2026-7525 | Medium 4.3 | Up to 3.7.9 | Fixed in a later version (latest 3.8.13) | 14 May 2026 |
| Cross-site scripting (XSS) CVE-2026-2355 | Medium 6.4 | Up to 3.7.3 | Fixed in a later version (latest 3.8.13) | 4 Mar 2026 |
| Cross-site scripting (XSS) CVE-2024-1274 | Medium 5.4 | Before 3.4.24 | Fixed in 3.4.24 | 2 Apr 2024 |
| SQL injection CVE-2023-6360 | High 8.6 | Before 3.4.22 | Fixed in 3.4.22 | 30 Nov 2023 |
| Cross-site scripting (XSS) CVE-2021-24927 | Medium 5.4 | Before 3.2.18 | Fixed in 3.2.18 | 29 Nov 2021 |
| Cross-site scripting (XSS) CVE-2019-15713 | Medium 6.1 | Before 3.1.10 | Fixed in 3.1.10 | 28 Aug 2019 |
| Cross-site scripting (XSS) CVE-2012-6527 | Not scored | Up to 1.10.1 | Fixed in a later version (latest 3.8.13) | 31 Jan 2013 |
Read the published descriptions
- CVE-2026-120117, 20 Nov 2026
- The My Calendar - Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'event_street' parameter in all versions up to, and including, 3.8.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that an administrator has granted the mc_add_events capability to Subscriber-level users via the plugin's Permissions settings; once granted, the Subscriber can store the payload without the mc_edit_locations capability because mc_admin_save() does not enforce it before calling mc_insert_location(). CVE record
- CVE-2026-118055, 20 Nov 2026
- The My Calendar - Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'event_title' parameter in all versions up to, and including, 3.8.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the plugin's documented permission grant to be applied, which allows Subscriber-level users to add and publish events; once granted, a self-submitted event title containing an entity-encoded payload is auto-published and fires in any visitor's browser upon clicking the event on the public calendar. CVE record
- CVE-2026-119088, 20 Nov 2026
- The My Calendar - Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'mc_template (template body); event_title (payload storage)' parameter in all versions up to, and including, 3.8.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires the site to have granted mc_add_events to Subscriber-level users (a configurable plugin permission), and relies on a privileged user - such as an Administrator - following the event preview link surfaced on the My Calendar Events management screen. CVE record
- CVE-2026-121538, 20 Nov 2026
- The My Calendar - Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'event_post (post ID) + event_title (XSS payload) + content (shortcode)' parameter in all versions up to, and including, 3.8.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires an administrator to have granted the mc_add_events capability to Subscriber-level or other lower-privileged roles, which is the plugin's documented workflow for allowing front-end event submissions. CVE record
- CVE-2026-119714, 30 Oct 2026
- My Calendar WordPress plugin 3.8.8 before 3.8.11 contains a shortcode injection vulnerability that allows unauthenticated attackers to execute registered shortcodes via the mcs search parameter. The mcs value reaches mc_search_results() in src/my-calendar-search.php without bracket encoding before do_shortcode runs, so a GET request triggers shortcodes on any page or post, enabling content injection and spoofing. CVE record
- CVE-2026-104798, 16 Oct 2026
- The My Calendar - Accessible Event Manager plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.8.7. The public `mcs` GET parameter is reflected into post content unsanitized before WordPress core's `do_shortcode` filter runs, allowing an unauthenticated attacker to inject a nested `[my_calendar above=...]` shortcode; `mc_generate_calendar_nav()` then splits the `above` attribute on commas and dispatches each element via `call_user_func()` with no authentication, authorization, or callable allowlist check. This makes it possible for unauthenticated attackers to invoke arbitrary loaded PHP functions, enabling a call chain in which the shortcode `$params` array is passed to `edit_user()` - which PHP coerces to integer `1` as the `$user_id` argument - overwriting the credentials of the initial Administrator account (user ID 1) and granting the attacker full wp-admin access. Exploitation is trivially reachable via the plugin's auto-generated `/my-calendar/` page, which is publicly accessible by default upon plugin activation. CVE record
- CVE-2026-77187, 9 Sep 2026
- The My Calendar - Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'before' and 'after' Shortcode Attributes in all versions up to, and including, 3.8.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-77186, 9 Sep 2026
- The My Calendar - Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'fallback' Shortcode Attribute in all versions up to, and including, 3.8.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The bypass relies on hex-encoded shortcode attribute payloads (e.g. \x3cscript\x3e), which wp_kses_post cannot strip on save because they appear as literal backslash sequences rather than real HTML tags; WordPress core's shortcode_parse_atts() then calls stripcslashes() at render time, decoding the escapes into real angle brackets before they reach the unescaped sink. CVE record
- CVE-2026-6854, 8 Jul 2026
- The My Calendar - Accessible Event Manager plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'mc_auth' parameter in all versions up to, and including, 3.7.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2026-11896, 2 Jul 2026
- 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. CVE record
- CVE-2026-7525, 14 May 2026
- The My Calendar - Accessible Event Manager plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.7.9. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with custom-level access and above, to bypass the moderation and approval workflow by tampering with the POST body to publish events or set other unauthorized statuses such as cancelled or private, in ways their role does not permit. While the UI correctly restricts low-privilege users to a draft-only submit button, this restriction is enforced only client-side, making it trivially bypassable by directly manipulating the POST request. CVE record
- CVE-2026-2355, 4 Mar 2026
- The My Calendar - Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `template` attribute of the `[my_calendar_upcoming]` shortcode in all versions up to, and including, 3.7.3. This is due to the use of `stripcslashes()` on user-supplied shortcode attribute values in the `mc_draw_template()` function, which decodes C-style hex escape sequences (e.g., `\x3c` to `<`) at render time, bypassing WordPress's `wp_kses_post()` content sanitization that runs at save time. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-1274, 2 Apr 2024
- The My Calendar WordPress plugin before 3.4.24 does not sanitise and escape some parameters, which could allow users with a role as low as Subscriber to perform Cross-Site Scripting attacks (depending on the permissions set by the admin) CVE record
- CVE-2023-6360, 30 Nov 2023
- The 'My Calendar' WordPress Plugin, version < 3.4.22 is affected by an unauthenticated SQL injection vulnerability in the 'from' and 'to' parameters in the '/my-calendar/v1/events' rest route. CVE record
- CVE-2021-24927, 29 Nov 2021
- The My Calendar WordPress plugin before 3.2.18 does not sanitise and escape the callback parameter of the mc_post_lookup AJAX action (available to any authenticated user) before outputting it back in the response, leading to a Reflected Cross-Site Scripting issue CVE record
- CVE-2019-15713, 28 Aug 2019
- The my-calendar plugin before 3.1.10 for WordPress has XSS. CVE record
- CVE-2012-6527, 31 Jan 2013
- Cross-site scripting (XSS) vulnerability in the My Calendar plugin before 1.10.2 for WordPress allows remote attackers to inject arbitrary web script or HTML via the PATH_INFO. CVE record
What to do if you run My Calendar
If you run My Calendar, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new My Calendar vulnerabilities
Free. We email you when a new vulnerability is published for My Calendar, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.