time spent vulnerabilities and fixes
Recent CVEs affecting time spent, with upgrade or downgrade steps. 3 tracked.
Also searched as: timespent.
time spent has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2012-12-03. Highest priority: CVE-2012-5550 (score 43/100).
- CVE-2012-5550 HIGH 7.5 DOWNGRADE SQL injection vulnerability in the Time Spent module 6.x and 7.x for Drupal allows remote attackers to execute
- CVE-2012-5549 MEDIUM 6.8 DOWNGRADE Cross-site request forgery (CSRF) vulnerability in the Time Spent module 6.x and 7.x for Drupal allows remote
- CVE-2012-5548 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in the Time Spent module 6.x and 7.x for Drupal allows remote attacke
FAQ
How do I fix time spent 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 time spent being exploited right now?
None of the tracked time spent CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which time spent CVE should I patch first?
CVE-2012-5550 currently ranks highest (43/100): SQL injection vulnerability in the Time Spent module 6.x and 7.x for Drupal allows remote attackers to execute.