My Calendar 3.8.14 fixes six reported security issues, all requiring authentication. In addition to fixing these six issues, it includes extensive additional hardening across the entire plugin, and fixes a handful of other bugs.
These security fixes have only been applied for the version 3.8 branch; if you are still on an older release, you are not protected.
If you are using My Calendar Pro, some of these changes may break behaviors on older versions of Pro or on Pro combined with older versions of My Calendar.
As a reminder, only the latest versions of My Calendar or My Calendar Pro are supported and expected to work fully together. If you need support to help update, don’t hesitate to contact me and request support!
Changes in 3.8.14
- Bug fix: Guard against inserting empty locations by omitting event_zoom from empty value test.
- Bug fix: Guard against non-existing event objects in schema generation.
- Bug fix: If calendar URI (Uniform Resource Identifier) not set, search did not render, though that’s not a requirement for search.
- Change: Remove checks for $_POST data in search. My Calendar search is never submitted via POST.
- Change: Set up calendar metaboxes on add_meta_box hook instead of admin_menu.
- Change: Remove jquery.stick library with CSS (Cascading Style Sheets).
- Security: Authenticated Stored Cross-Site Scripting via event_post. Props @wordfence and @jiahao.
- Security: Authenticated Stored Cross-Site Scripting via event_street. Props @wordfence and @jiahao.
- Security: Authenticated Stored Cross-Site Scripting via event_title. Props @wordfence and @jiahao.
- Security: Authenticated Stored Cross-Site Scripting via event_title. Props @wordfence and @braintx.
- Security: Authenticated Stored Cross-Site Scripting via template shortcode parameter. Props @avrlab233.
- Security: Authenticated Missing Authorization check allowing event deletion. Props @duck4nh.
- Security: Extensive hardening across entire plugin.
- Tooling: Expand e2e and PHP (Hypertext PreProcessing) unit tests.





