SpiderCalendar

SpiderCalendar has 4 disclosed vulnerabilities in the WordSec catalog, reported between 2015 and 2022; all 4 are fixed as of September 2026. Their average CVSS score is 8.6, and the most serious one scores 9.8 out of 10. Severity breakdown: 2 critical and 1 high. 2015 was the busiest year with 2 disclosures.

The most common weakness is SQL Injection, behind 2 of the records (50%). Other recurring categories include Cross-Site Request Forgery (CSRF), Cross-Site Scripting.

Every one of the 4 issues recorded for SpiderCalendar has a vendor fix available, so running the current release closes all known holes.

3 independent researchers contributed these findings, one record each.

Strategic Overview

Avg CVSSHigh

8.6/ 10

Patch Coverage100%

Open

Fixed

Get automatic notifications for all SpiderCalendar vulnerabilities before they are exploited.

Highest severity on recordCVSS 9.8CVE-2017-7719

SpiderCalendar <= 1.5.51 - SQL Injection

Read the full analysis

Vulnerability Records

4 records


2022-01-13 00:00	SpiderCalendar <= 1.6.64 - Reflected Cross-Site Scripting SpiderCalendar <= 1.5.65	`CVE-2022-0212`	6.1 Medium	Krzysztof Zając	Yes
2017-04-10 00:00	SpiderCalendar <= 1.5.51 - SQL Injection SpiderCalendar <= 1.5.51	`CVE-2017-7719`	9.8 Critical	Manuel Garcia Cardenas	Yes
2015-03-11 00:00	SpiderCalendar <= 1.4.13 - Cross-Site Request Forgery SpiderCalendar <= 1.4.13	`N/A`	8.8 High	Anonymous	Yes
2015-02-13 00:00	SpiderCalendar <= 1.4.9 - Unauthenticated SQL Injection SpiderCalendar < 1.4.10	`CVE-2015-2196`	9.8 Critical	Mateusz Lach	Yes

Showing 1–4 of 4 reports