WordPress plugin · calendar
Is Calendar safe?
Safe on 1.3.18 or newer.
The current version, 1.3.18, is past every affected range on record (4 of 4 records list one). Keep it updated and you’re clear of them.
- Flaws on record
- 4
- High or critical
- 1
- Exploited
- none
- Current version
- 1.3.18
- Last updated
- May 16, 2026
- Active installs
- 4,000+
Every recorded flaw
- Jul 27, 2026Calendar: Does not properly escape a user-supplied event field before outputting it inside an HTML attribute on a public-facing pageCVE-2026-14827 · fixed in 1.3.18 · reported by WPScanMedium 6.8
- Dec 23, 2025Calendar: Stored Cross-Site ScriptingCVE-2025-14548 · affects up to 1.3.16 · reported by WordfenceMedium 6.4
- May 2, 2024Calendar: SQL InjectionCVE-2024-2831 · affects up to 1.3.14 · reported by WordfenceHigh 8.8
- May 27, 2014Cross-site request forgery (CSRF) vulnerability in the Calendar plugin before 1.3.3 for WordPress allows remote attackers to hijack the authentication of users CVE-2013-2698 · fixed in 1.3.3 · reported by PSIRT-CNA@flexerasoftware.com1.1% oddsMedium 6.8
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.