PatchTheCVEphpstatus vulnerabilities and fixes
Recent CVEs affecting phpstatus, with upgrade or downgrade steps. 3 tracked.
phpstatus has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2006-02-07. Highest priority: CVE-2006-0572 (score 45/100).
- CVE-2006-0572 HIGH 7.5 DOWNGRADE phpstatus 1.0 does not require passwords when using cookies to identify a user, which allows remote attackers
- CVE-2006-0571 MEDIUM 4.3 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in phpstatus 1.0 allow remote attackers to inject arbitrar
- CVE-2006-0570 HIGH 7.5 DOWNGRADE Multiple SQL injection vulnerabilities in phpstatus 1.0, when gpc_magic_quotes is disabled, allow remote attac
FAQ
How do I fix phpstatus 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 phpstatus being exploited right now?
None of the tracked phpstatus CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which phpstatus CVE should I patch first?
CVE-2006-0572 currently ranks highest (45/100): phpstatus 1.0 does not require passwords when using cookies to identify a user, which allows remote attackers .