CVE-2026-120117: My Calendar <= 3.8.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'event_street' Address Field
The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'eventstreet' 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 mcaddevents capability to Subscriber-level users via the plugin's Permissions settings; once granted, the Subscriber can store the payload without the mceditlocations capability because mcadminsave() does not enforce it before calling mcinsertlocation().
Affected Software
Event History
Frequently Asked Questions
Which sites are exposed to exploitation by Subscriber-level accounts?
Exploitation requires an administrator to have granted the plugin's mc_add_events capability to Subscriber-level users in the plugin's Permissions settings. Subscribers do not need the mc_edit_locations capability because the affected save path does not enforce it before inserting the location.
What access does an attacker need to trigger the issue?
The attacker must be authenticated with at least Subscriber-level access and must be able to add events through the mc_add_events capability. They can place a script payload in the event_street address field, which executes when another user accesses the affected page.
What can be done if updating is not immediately possible?
Remove mc_add_events from Subscriber-level users in the plugin's Permissions settings. Review event address data, particularly event_street values created by lower-privileged accounts, for injected script content.