hashtopussy vulnerabilities and fixes
Recent CVEs affecting hashtopussy, with upgrade or downgrade steps. 2 tracked.
hashtopussy has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2017-07-27. Highest priority: CVE-2017-11681 (score 53/100).
- CVE-2017-11681 HIGH 8.8 UPGRADE Incorrect Access Control vulnerability in Hashtopussy 0.4.0 allows remote authenticated users to execute actio
- CVE-2017-11680 HIGH 8.8 UPGRADE Cross-Site Request Forgery (CSRF) exists in Hashtopussy 0.4.0, allowing an admin password change via users.php
FAQ
How do I fix hashtopussy 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 hashtopussy being exploited right now?
None of the tracked hashtopussy CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which hashtopussy CVE should I patch first?
CVE-2017-11681 currently ranks highest (53/100): Incorrect Access Control vulnerability in Hashtopussy 0.4.0 allows remote authenticated users to execute actio.