SpiderCalendar vulnerabilities
Plugin slug spider-event-calendar · 4 known vulnerabilities · latest disclosed 2022-01-13 · WordPress.org page
Every listed vulnerability has a fix. Version 1.6.65 or later is not affected by any of them. If your site runs an older version, update it.
3 of 4 rated high or critical (CVSS 7 or more).
Known vulnerabilities in SpiderCalendar
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 6.1 | <= 1.5.65 | 1.6.65 | CVE-2022-0212 | 2022-01-13 | Advisory |
| Critical 9.8 | <= 1.5.51 | 1.5.52 | CVE-2017-7719 | 2017-04-10 | Advisory |
| High 8.8 | <= 1.4.13 | 1.4.14 | none | 2015-03-11 | Advisory |
| Critical 9.8 | < 1.4.10 | 1.4.10 | CVE-2015-2196 | 2015-02-13 | Advisory |
Check if a site is affected
Enter a site address to see which version of SpiderCalendar and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the SpiderCalendar plugin safe to use?
All 4 known issues are fixed in current versions (1.6.65 or later). Keeping it updated is what matters.
How do I check which version of SpiderCalendar my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.