PatchTheCVEsphider vulnerabilities
Recent CVEs affecting sphider products. 4 tracked.
sphider has 4 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 4. Most recent: 2020-02-10. Highest priority: CVE-2014-5087 (score 68/100).
- CVE-2014-5087 CRITICAL 9.8 UPGRADE UPGRADE A vulnerability exists in Sphider Search Engine prior to 1.3.6 due to exec calls in admin/spiderfuncs.php, whi
- CVE-2014-5086 HIGH 8.8 UPGRADE UPGRADE A Command Execution vulnerability exists in Sphider Pro, and Sphider Plus 3.2 due to insufficient sanitization
- CVE-2014-5083 HIGH 8.8 UPGRADE A Command Execution vulnerability exists in Sphider before 1.3.6 due to insufficient sanitization of fwrite to
- CVE-2014-5081 CRITICAL 9.8 UPGRADE UPGRADE sphider prior to 1.3.6, sphider-pro prior to 3.2, and sphider-plus prior to 3.2 allow authentication bypass
FAQ
How do I fix sphider vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is sphider being exploited right now?
None of the tracked sphider CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which sphider CVE should I patch first?
CVE-2014-5087 currently ranks highest (68/100): A vulnerability exists in Sphider Search Engine prior to 1.3.6 due to exec calls in admin/spiderfuncs.php, whi.