bad behavior vulnerabilities and fixes
Recent CVEs affecting bad behavior, with upgrade or downgrade steps. 2 tracked.
Also searched as: badbehavior.
bad behavior has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2014-11-12. Highest priority: CVE-2012-4271 (score 40/100).
- CVE-2014-8735 MEDIUM 4.0 DOWNGRADE The Bad Behavior module 6.x-2.x before 6.x-2.2216 and 7.x-2.x before 7.x-2.2216 for Drupal logs usernames and
- CVE-2012-4271 MEDIUM 4.3 UPGRADE MITIGATE Multiple cross-site scripting (XSS) vulnerabilities in bad-behavior-wordpress-admin.php in the Bad Behavior pl
FAQ
How do I fix bad behavior 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 bad behavior being exploited right now?
None of the tracked bad behavior CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which bad behavior CVE should I patch first?
CVE-2012-4271 currently ranks highest (40/100): Multiple cross-site scripting (XSS) vulnerabilities in bad-behavior-wordpress-admin.php in the Bad Behavior pl.