Plugins · pretty-google-calendar · data as of 2026-11-04
Is Pretty Google Calendar safe? Known vulnerabilities and latest version
- Latest version
- 2.2.1
- Last updated
- 2026-01-04
- Active installs
- 4,000+
- Known issues on record
- 2
- Unpatched in latest
- 0
- Tested up to WP
- 6.9.11
Embedded Google Calendars that don't suck. — by LBell
What to do
- Update to the latest version (2.2.1). Anything older than 2.0.1 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- 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 pretty-google-calendar --field=version shows what you run; wp plugin update pretty-google-calendar 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 5.3 CVE-2025-12898 · published 2025-12-20
Missing authorization check in Pretty Google Calendar (2.0.0 and older)
- Affected
- 2.0.0 and older
- Fixed in
- 2.0.1 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Pretty Google Calendar plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the pgcal_ajax_handler() function in all versions up to, and including, 2.0.0. This makes it possible for unauthenticated attackers to retrieve the Google API key set in the plugin's settings.
NVD CVE-2025-12898Wordfence advisoryCode change (fix)wordpress.org
medium 6.5 CVE-2024-33640 · published 2024-04-29
Stored cross-site scripting (XSS) in Pretty Google Calendar (1.7.2 and older)
- Affected
- 1.7.2 and older
- Fixed in
- 2.0.0 *
- 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 Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LBell Pretty Google Calendar allows Stored XSS.This issue affects Pretty Google Calendar: from n/a through 1.7.2.
Recent activity
- 2026-01-04 — latest release on wordpress.org (2.2.1).
- 2025-12-20 — Missing authorization check disclosed (CVE-2025-12898), fixed in 2.0.1.
- 2024-04-29 — Stored cross-site scripting (XSS) disclosed (CVE-2024-33640), fixed in 2.0.0.
Get an email when Pretty Google Calendar has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Pretty Google Calendar (pretty-google-calendar) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Missing authorization (1) · Cross-site scripting (XSS) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/pretty-google-calendar (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/pretty-google-calendar"><img src="https://laskyr.com/plugins/pretty-google-calendar/badge.svg" alt="Pretty Google Calendar vulnerability status"></a>