rankem vulnerabilities and fixes
Recent CVEs affecting rankem, with upgrade or downgrade steps. 4 tracked.
rankem has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2009-01-22. Highest priority: CVE-2008-5589 (score 47/100).
- CVE-2009-0249 MEDIUM 5.0 MITIGATE Katy Whitton RankEm stores sensitive information under the web root with insufficient access control, which al
- CVE-2009-0248 MEDIUM 4.3 MITIGATE Cross-site scripting (XSS) vulnerability in rankup.asp in Katy Whitton RankEm allows remote attackers to injec
- CVE-2008-5589 HIGH 7.5 MITIGATE SQL injection vulnerability in processlogin.asp in Katy Whitton RankEm allows remote attackers to execute arbi
- CVE-2008-5588 HIGH 7.5 MITIGATE SQL injection vulnerability in rankup.asp in Katy Whitton RankEm allows remote attackers to execute arbitrary
FAQ
How do I fix rankem 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 rankem being exploited right now?
None of the tracked rankem CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which rankem CVE should I patch first?
CVE-2008-5589 currently ranks highest (47/100): SQL injection vulnerability in processlogin.asp in Katy Whitton RankEm allows remote attackers to execute arbi.