Google Calendar Events <= 4.3.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Google Calendar ID Setting
- ID
- WPSEC-2026-3277
- Plugin
- Simple Calendar – Google Calendar, Events, & ICS Feeds (google-calendar-events)
- Affected
- from 4.0.6 before 4.3.3
- Remediation
- Update to 4.3.3 or later.
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- Weakness
- CWE-79
- Usage
- Plugin Medium · Affected versions Low among sites WPSec scans, 2026-11-17
- Attack surface
- Google Calendar Events on WPSec AttackSurface
- Fix released
- Published
Description
The Google Calendar, Events, & ICS Feeds plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the calendar's 'Calendar ID' setting in all versions up to, and including, 4.3.2. This is due to insufficient input sanitization and output escaping: the Google Calendar ID is saved with sanitize_text_field(), which keeps quotes, and the settings field decodes it with a custom callback that replaces the plugin's default attribute escaping before it is printed into the input's value attribute. This makes it possible for authenticated attackers with contributor-level access and above, who can create and edit calendars, to inject arbitrary web scripts that execute when another user, such as an administrator, opens the calendar's edit screen.
References
- https://wpsec.com/vuln/WPSEC-2026-3277/
- https://plugins.svn.wordpress.org/google-calendar-events/tags/4.3.3/
- https://wordpress.org/plugins/google-calendar-events/
Published by WPSec. Provided as is, without warranty. Corrections: contact us.
This advisory as JSON or Markdown · All advisories: JSON, RSS