PatchTheCVEphprank vulnerabilities and fixes
Recent CVEs affecting phprank, with upgrade or downgrade steps. 4 tracked.
phprank has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2002-12-31. Highest priority: CVE-2002-1952 (score 50/100).
- CVE-2002-1952 HIGH 7.5 DOWNGRADE phpRank 1.8 does not properly check the return codes for MySQL operations when authenticating users, which cou
- CVE-2002-1950 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in phpRank 1.8 allows remote attackers to inject arbitrary web script
- CVE-2002-1800 HIGH 7.5 DOWNGRADE phpRank 1.8 stores the administrative password in plaintext on the server and in the "ap" cookie, which allows
- CVE-2002-1799 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in phpRank 1.8 allows remote attackers to inject arbitrary web script
FAQ
How do I fix phprank 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 phprank being exploited right now?
None of the tracked phprank CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which phprank CVE should I patch first?
CVE-2002-1952 currently ranks highest (50/100): phpRank 1.8 does not properly check the return codes for MySQL operations when authenticating users, which cou.