SpiderVPlayer Vulnerabilities
The SpiderVPlayer WordPress plugin has 3 known security vulnerabilities. The most recent was disclosed on July 19, 2016. Check whether your site runs an affected version below.
View SpiderVPlayer on WordPress.orgSummary
Latest vulnerability disclosed on July 19, 2016.
Recommendation
WPSentry recommends installing with caution
Use SpiderVPlayer 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 SpiderVPlayer and 35+ other WordPress security checks — no login or plugin required.
Known SpiderVPlayer vulnerabilities
- high
SpiderVPlayer < 1.5.18 - Multiple Blind Authenticated SQL Injections
Affected versions: <1.5.18Disclosed July 19, 2016 - medium
SpiderVPlayer< 1.5.5 - Reflected Cross-Site Scripting
Affected versions: <1.5.5Disclosed February 2, 2015 - medium
SpiderVPlayer <= 2.1 - Reflected Cross-Site Scripting
Affected versions: <=2.1Disclosed December 9, 2013
How to stay protected
Update promptly
Keep SpiderVPlayer 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.