WordPress plugin
SpiderCalendar security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 4 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical2
- High1
- Medium1
- Low0
All SpiderCalendar vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Critical9.8 | SQL Injection ≤1.5.51Update to 1.5.52 | CVE-2017-7719 | |
| High8.8 | Cross-Site Request Forgery ≤1.4.13Update to 1.4.14 | — | |
| Critical9.8 | Unauthenticated SQL Injection <1.4.10Update to 1.4.10 | CVE-2015-2196 |
- Critical9.8SQL Injection
≤1.5.51Update to 1.5.52
- High8.8Cross-Site Request Forgery
≤1.4.13Update to 1.4.14
- Critical9.8Unauthenticated SQL Injection
<1.4.10Update to 1.4.10
SpiderCalendar: common questions
Does SpiderCalendar have known vulnerabilities?
Yes. VulnCrest Radar lists 4 known vulnerabilities in SpiderCalendar: 2 critical, 1 high, 1 medium. None are known to affect version null.
How do I check which version of SpiderCalendar I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent SpiderCalendar vulnerability?
CVE-2022-0212, published Jan 13, 2022: SpiderCalendar <= 1.6.64 - Reflected Cross-Site Scripting. Severity: Medium (CVSS 6.1).
Is any SpiderCalendar vulnerability listed in CISA KEV?
No. None of the known SpiderCalendar vulnerabilities is currently listed in the CISA KEV catalog.