Skip to content
Laskyr

Plugins · private-google-calendars · data as of 2026-11-04

Is Private Google Calendars safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (20251206)

As of 2026-11-04. 2 issues are on record for older versions.

Latest version
20251206
Last updated
2025-12-06
Active installs
1,000+
Known issues on record
2
Unpatched in latest
0
Tested up to WP
6.9.11 · PHP 5.4.0+

Display private and public Google Calendars on your Wordpress website. — by michielve

What to do

  1. Update to the latest version (20251206). Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get private-google-calendars --field=version shows what you run; wp plugin update private-google-calendars updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 4.3 CVE-2025-12526 · published 2025-11-11

Missing authorization check in Private Google Calendars (20250811 and older)

Affected
20250811 and older
Fixed in
unknown
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Private Google Calendars plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'pgc_remove' action in all versions up to, and including, 20250811. This makes it possible for authenticated attackers, with Subscriber-level access and above, to reset the plugin's settings.

NVD CVE-2025-12526Wordfence advisoryCode change (fix)wordpress.org

medium 5.4 CVE-2023-52198 · published 2024-01-08

Stored cross-site scripting (XSS) in Private Google Calendars (20231125 and older)

Affected
20231125 and older
Fixed in
unknown
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by NVD
Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Michiel van Eerd Private Google Calendars allows Stored XSS.This issue affects Private Google Calendars: from n/a through 20231125.

NVD CVE-2023-52198Patchstack advisory

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Private Google Calendars vulnerability status badge
<a href="https://laskyr.com/plugins/private-google-calendars"><img src="https://laskyr.com/plugins/private-google-calendars/badge.svg" alt="Private Google Calendars vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit