Private Google Calendars <= 20250811 - Missing Authorization to Authenticated (Subscriber+) Settings Reset
Strategic Overview
- Status
- Patched in 20251128
- Affected Plugin
- Private Google Calendars
- Affected Version
<= 20250811- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-12526
At a glance
CVE-2025-12526 is a medium-severity Missing Authorization vulnerability in the Private Google Calendars WordPress plugin, affecting versions <= 20250811. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 20251128; sites on affected versions should update now. Disclosed November 2025, reported by Athiwat Tiprasaharn (Jitlada).
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Private Google Calendars <= 20250811 carries this weakness at pgc_remove, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Private Google Calendars the fix is 20251128: builds <= 20250811 are affected, anything from 20251128 onward is not.
Remediation
Update to version 20251128, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Private Google Calendars 20251128 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Private Google Calendars
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C