Spiffy Calendar
spiffy-calendar · plugin
Known security vulnerabilities for Spiffy Calendar. Find out in seconds which version runs on your site with WP Lens.
12 known vulnerabilities
1 critical · 4 exploitable without logging in · latest Dec 24, 2025
Listed on wordpress.org · latest 5.0.11 · last updated Apr 17, 2026 · 2K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Critical 9.8
CVE-2022-46859login required≤ 4.9.1
WordPress Spiffy Calendar Plugin <= 4.9.1 is vulnerable to SQL Injection
- High 7.6
CVE-2024-43969high privilege≤ 4.9.12
WordPress Spiffy Calendar plugin <= 4.9.12 - SQL Injection vulnerability
- High 7.2
CVE-2024-38692high privilege≤ 4.9.11
WordPress spiffy-calendar plugin <= 4.9.11 - SQL Injection vulnerability
- Medium 6.3
CVE-2024-30528login required≤ 4.9.10
WordPress Spiffy Calendar plugin <= 4.9.10 - Broken Access Control vulnerability
- Medium 6.1
CVE-2024-45458unauthenticated · needs a click≤ 4.9.13
WordPress Spiffy Calendar plugin <= 4.9.13 - Reflected Cross Site Scripting (XSS) vulnerability
- Medium 6.1
CVE-2024-30427unauthenticated · needs a click≤ 4.9.7
WordPress Spiffy Calendar plugin <= 4.9.7 - Cross Site Scripting (XSS) vulnerability
- Medium 6.1
CVE-2023-32122unauthenticated · needs a click≤ 4.9.3
WordPress Spiffy Calendar Plugin <= 4.9.3 is vulnerable to Cross Site Scripting (XSS)
- Medium 5.4
CVE-2024-45457login required≤ 4.9.13
WordPress Spiffy Calendar plugin <= 4.9.13 - Cross Site Scripting (XSS) vulnerability
- Medium 5.4
CVE-2023-49745login required≤ 4.9.5
WordPress Spiffy Calendar Plugin <= 4.9.5 is vulnerable to Cross Site Scripting (XSS)
- Medium 5.4
CVE-2022-29434login required≤ 4.9.0
WordPress Spiffy Calendar plugin <= 4.9.0 - Edit/Delete event via IDOR vulnerability
- Medium 4.3
CVE-2022-25599unauthenticated · needs a click≤ 4.9.0
WordPress Spiffy Calendar plugin <= 4.9.0 - Event deletion via Cross-Site Request Forgery (CSRF) vulnerability
- Medium 4.3
CVE-2025-68523login required≤ 5.0.7
WordPress Spiffy Calendar plugin <= 5.0.7 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).