Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

Pretty Google Calendar Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 3 vulnerability records associated with Pretty Google Calendar, published between 2023 and 2025.

Dataset last synchronized: 2026-08-03 00:31:25 UTC

At a glance

Security Snapshot

3Total records
0Critical
0High
3Medium
0Low
0Informational
3Patched records
0Currently marked unpatched
2023-09-25First disclosure
2025-12-19Latest disclosure
2 of 3CVE coverage

Use this history

Check and watch Pretty Google Calendar.

A history record does not establish whether the version installed on your website is affected. Enter the exact version in the checker, or add this software to a private Critical/High alert watchlist.

Year-by-Year Timeline

YearRecordsRelative volume
202311 records
202411 records
202511 records

Severity Breakdown

SeverityRecordsShare
Medium3100%

Vulnerability-Type Breakdown

Cross-Site Scripting

2 records66.7%

First: 2023. Latest: 2024.

Missing Authorization

1 record33.3%

First: 2025. Latest: 2025.

Patch Status

Patched
3
Currently marked unpatched
0
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 2.0.1
  • 2.0.0
  • 1.6.0

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-2.0.0Pretty Google Calendar <= 2.0.0 - Missing Authorization to Unauthenticated Google API Key ExposureDecember 19, 20252.0.1Medium
*-1.7.2Pretty Google Calendar <= 1.7.2 - Authenticated (Contributor+) Stored Cross-Site ScriptingApril 25, 20242.0.0Medium
[*, 1.6.0)Pretty Google Calendar <= 1.5.1 - Authenticated(Contributor+) Stored Cross-Site Scripting via pretty_google_calendar shortcodeSeptember 25, 20231.6.0Medium

Selected source records

Latest Records

MediumCVE-2025-12898

Pretty Google Calendar <= 2.0.0 - Missing Authorization to Unauthenticated Google API Key Exposure

Published: December 19, 2025

Affected versions
*-2.0.0
Patched versions
2.0.1
Original Wordfence record
MediumCVE-2024-33640

Pretty Google Calendar <= 1.7.2 - Authenticated (Contributor+) Stored Cross-Site Scripting

Published: April 25, 2024

Affected versions
*-1.7.2
Patched versions
2.0.0
Original Wordfence record
Medium

Pretty Google Calendar <= 1.5.1 - Authenticated(Contributor+) Stored Cross-Site Scripting via pretty_google_calendar shortcode

Published: September 25, 2023

Affected versions
[*, 1.6.0)
Patched versions
1.6.0
Original Wordfence record

Highest-Severity Records

Medium

Pretty Google Calendar <= 1.5.1 - Authenticated(Contributor+) Stored Cross-Site Scripting via pretty_google_calendar shortcode

Published: September 25, 2023

Affected versions
[*, 1.6.0)
Patched versions
1.6.0
Original Wordfence record
MediumCVE-2024-33640

Pretty Google Calendar <= 1.7.2 - Authenticated (Contributor+) Stored Cross-Site Scripting

Published: April 25, 2024

Affected versions
*-1.7.2
Patched versions
2.0.0
Original Wordfence record
MediumCVE-2025-12898

Pretty Google Calendar <= 2.0.0 - Missing Authorization to Unauthenticated Google API Key Exposure

Published: December 19, 2025

Affected versions
*-2.0.0
Patched versions
2.0.1
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory