The SpiderCalendar WordPress plugin through 1.5.65 does not sanitise and escape the callback parameter before outputting it back in the page via the window AJAX action (available to both unauthenticated and authenticated users), leading to a Reflected Cross-Site Scripting issue.
Product
wordpress spider-event-calendar vulnerabilities
4 published CVES affecting wordpress spider-event-calendar, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 4
- Critical
- 1
- High
- 2
- Medium
- 1
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress spider-event-calendar CVEs
Newest publication first
-
MediumCVSS 6.1 EPSS 2.3%
-
CriticalCVSS 9.8 EPSS 2.3%
SQL injection in the Spider Event Calendar (aka spider-event-calendar) plugin before 1.5.52 for WordPress is exploitable with the order_by parameter to calendar_functions.php or widget_Theme_functions.php, related to front_end/frontend_functions.php.
-
WORDFENCE-e597b677-e298-4507-86a5-70a93a9afd6e SpiderCalendar <= 1.4.13 - Cross-Site Request Forgery
PublishedHighCVSS 8.8The SpiderCalendar plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.4.13. This is due to missing or incorrect nonce validation on the Manage_Spider_Calendar() function. This makes it possible for unauthenticated attackers to mak...
-
HighCVSS 7.5 EPSS 10.9% Public exploit
SQL injection vulnerability in Spider Event Calendar 1.4.9 for WordPress allows remote attackers to execute arbitrary SQL commands via the cat_id parameter in a spiderbigcalendar_month action to wp-admin/admin-ajax.php.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.