Private Google Calendars
Private Google Calendars has 2 disclosed vulnerabilities in the WordSec catalog, reported between 2024 and 2025; all 2 are fixed as of September 2026. Their average CVSS score is 5.3, and the most serious one scores 6.4 out of 10.
The most common weakness is Cross-Site Scripting, behind 1 of the records (50%). Other recurring categories include Missing Authorization.
Every one of the 2 issues recorded for Private Google Calendars has a vendor fix available, so running the current release closes all known holes.
2 independent researchers contributed these findings, one record each. Private Google Calendars is installed on roughly 1,000 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 6.9.7.
CVE-2023-52198Private Google Calendars <= 20231125 - Authenticated (Contributor+) Stored Cross-Site Scripting
Read the full analysisVulnerability Records

Private Google Calendars
Author
michielve
If you update to version 20230111, please note that: The theming has slightly been changed. Now there is distinction between bundled and custom themes. The previously bundled dark and light themes have been renamed. So if you used these themes, you now have to manually update these themes to the new pgc-dark and pgc-light themes. The popup theme has been removed. This can now be set in your custom theme. See for details about this release: https://blog.michielvaneerd.nl/wordpress-plugins/private-google-calendars/version-20230111-details/ This plugin can display multiple private and public Google calendars with a shortcode, Gutenberg block or as a widget. See the webpage for more information. Features Access to private (and public) calendars by using OAuth2 or an API key. Adjustable caching – this can greatly improve the performance. It uses the FullCalendar library to show the calendar and can be fully customized within the Gutenberg block, shorcode attributes and the widget settings. Calendar filtering.
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C