SpiderCalendar Vulnerabilities
The SpiderCalendar WordPress plugin has 1 known security vulnerability. The most recent was disclosed on March 11, 2015. Check whether your site runs an affected version below.
View SpiderCalendar on WordPress.orgSummary
Latest vulnerability disclosed on March 11, 2015.
Recommendation
WPSentry recommends installing with caution
Use SpiderCalendar only with care. This plugin has a history of high-severity vulnerabilities — always run the latest version and monitor it for newly disclosed issues.
Is your site affected?
Run a free external scan to detect SpiderCalendar and 35+ other WordPress security checks — no login or plugin required.
Known SpiderCalendar vulnerabilities
- high
SpiderCalendar <= 1.4.13 - Cross-Site Request Forgery
Affected versions: <=1.4.13Disclosed March 11, 2015
How to stay protected
Update promptly
Keep SpiderCalendar on its latest release — most vulnerabilities are fixed in newer versions.
Scan regularly
Run an external scan after every update to catch outdated or vulnerable software early.
Monitor continuously
Enable monitoring to get alerted the moment a new issue affects your stack.