SpiderVPlayer vulnerabilities
Plugin slug player · 7 known vulnerabilities · latest disclosed 2023-11-23 · WordPress.org page
4 vulnerabilities have no fixed version yet. If you use this plugin, consider disabling or replacing it until a fix is released.
2 of 7 rated high or critical (CVSS 7 or more).
Known vulnerabilities in SpiderVPlayer
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 4.4 | <= 1.5.22 | No fix yet | CVE-2023-48320 | 2023-11-23 | Advisory |
| Medium 6.1 | <= 1.5.22 | No fix yet | CVE-2023-45632 | 2023-10-11 | Advisory |
| High 8.8 | < 1.5.18 | 1.5.18 | none | 2016-07-19 | Advisory |
| Medium 6.1 | < 1.5.5 | 1.5.5 | none | 2015-02-02 | Advisory |
| Medium 6.1 | <= 1.5.1 | 1.5.2 | CVE-2014-8584 | 2014-11-11 | Advisory |
| Medium 6.1 | <= 2.1 | No fix yet | none | 2013-12-09 | Advisory |
| Critical 9.8 | <= 2.1 | No fix yet | CVE-2013-3532 | 2013-04-11 | Advisory |
Check if a site is affected
Enter a site address to see which version of SpiderVPlayer and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the SpiderVPlayer plugin safe to use?
4 known issue(s) have no fix yet, so check the table above before using it.
How do I check which version of SpiderVPlayer my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.