HomeWordPress vulnerabilitiesSpiffy Calendar
Spiffy Calendar vulnerabilities
Spiffy Calendar has 4 known vulnerabilities in this database. The most recent published record is dated 27 Feb 2024.
- Known vulnerabilities
- 4
- Active installs
- 2,000+
- Latest version
- 5.0.11
- Last updated
- 17 Apr 2026
- Most recent
- 27 Feb 2024
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Security weakness CVE-2024-0855 | Medium 5.3 | Before 4.9.9 | Fixed in 4.9.9 | 27 Feb 2024 |
| Broken access control CVE-2022-29434 | Medium 6.3 | Up to 4.9.0 | Fixed in a later version (latest 5.0.11) | 20 May 2022 |
| Cross-site request forgery (CSRF) CVE-2022-25599 | Medium 5.4 | Up to 4.9.0 | Fixed in a later version (latest 5.0.11) | 21 Feb 2022 |
| Cross-site scripting (XSS) CVE-2017-9420 | Medium 6.1 | Before 3.3.0 | Fixed in 3.3.0 | 5 Jun 2017 |
Read the published descriptions
- CVE-2024-0855, 27 Feb 2024
- The Spiffy Calendar WordPress plugin before 4.9.9 doesn't check the event_author parameter, and allows any user to alter it when creating an event, leading to deceiving users/admins that a page was created by a Contributor+. CVE record
- CVE-2022-29434, 20 May 2022
- Insecure Direct Object References (IDOR) vulnerability in Spiffy Plugins Spiffy Calendar <= 4.9.0 at WordPress allows an attacker to edit or delete events. CVE record
- CVE-2022-25599, 21 Feb 2022
- Cross-Site Request Forgery (CSRF) vulnerability leading to event deletion was discovered in Spiffy Calendar WordPress plugin (versions <= 4.9.0). CVE record
- CVE-2017-9420, 5 Jun 2017
- Cross site scripting (XSS) vulnerability in the Spiffy Calendar plugin before 3.3.0 for WordPress allows remote attackers to inject arbitrary JavaScript via the yr parameter. CVE record
What to do if you run Spiffy Calendar
If you run Spiffy Calendar, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Spiffy Calendar vulnerabilities
Free. We email you when a new vulnerability is published for Spiffy Calendar, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.