Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

Spiffy Calendar · Security record

Is Spiffy Calendar safe?

No known vulnerability affects the current version (5.0.11). 18 issues were found in earlier versions and fixed, the latest disclosed on Dec 24, 2025.

Checked 3 days ago against the WPVulnerability database, for version 5.0.11.

How it’s looked after

Last release
Apr 17, 2026 (6 months ago)
Releases in the last year
4
Tested up to
WordPress 6.9.11 (current: 7.1)
Support resolved
0 of 1 threads in two months
Active installs
2K+

18 known vulnerabilities

  • 4 high
  • 10 medium
  • 4 not rated

None affects the current version.

Disclosed each year

  • 20171
  • 20227
  • 20232
  • 20247
  • 20251

Every known vulnerability in Spiffy Calendar

Newest first, with any that affect the current version at the top.

Questions about Spiffy Calendar’s security

Is Spiffy Calendar safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Spiffy Calendar updated: most attacks target sites that haven’t updated.

Does Spiffy Calendar have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 18 older issues, fixed in earlier versions, so keep Spiffy Calendar up to date.

Is Spiffy Calendar still maintained?

Its last release was 6 months ago. Its authors resolved 0 of the 1 support threads opened in the last two months.

Is Spiffy Calendar compatible with the latest WordPress?

Spiffy Calendar’s readme says it’s tested up to WordPress 6.9.11, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.