WordPress spiffy-calendar has 4 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.
| CVE | Title | Severity | CVSS | Affected | Fixed in |
|---|---|---|---|---|---|
| CVE-2017-9420 | Cross site scripting (XSS) vulnerability in the Spiffy Calendar plugin before 3.3.0 for WordPress allows remote attackers to inject arbitrar | medium | 6.1 | =1.0.0 or =1.0.1 or =1.0.2a or =1.0.3 or =1.1.0 or =1.1.1 or =1.1.2 or =1.1.3 or =1.1.4 or =1.1.5 or =1.1.6 or =1.1.7 or =1.1.8 or =1.2.0 or =1.2.1 or =1.3.0 or =1.3.1 or =2.0.0 or =2.0.1 or =2.1.0 or =2.1.1 or =2.1.2 or =2.1.3 or =3.0.0 or =3.0.1 or =3.0.2 or =3.0.3 or =3.0.4 or =3.0.5 or =3.0.6 or =3.0.7 or =3.0.8 or =3.1.0 or =3.1.1 or =3.1.2 or =3.1.3 or =3.1.4 or =3.1.5 or =3.2.0 | – |
| CVE-2022-29434 | Insecure Direct Object References (IDOR) vulnerability in Spiffy Plugins Spiffy Calendar <= 4.9.0 at WordPress allows an attacker to edit or | medium | 6.3 | <=4.9.0 | – |
| CVE-2024-0855 | 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 | medium | 5.3 | <4.9.9 | 4.9.9 |
| CVE-2022-25599 | Cross-Site Request Forgery (CSRF) vulnerability leading to event deletion was discovered in Spiffy Calendar WordPress plugin (versions <= 4. | medium | 5.4 | <=4.9.0 | – |
Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.
# PHP projects (recommended) composer require --dev phpwarden/phpwarden # then vendor/bin/phpwarden wordpress /var/www/html # or, without Composer pipx install phpwarden && phpwarden wordpress /var/www/html
Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.
Install docs How findings are ranked