PatchTheCVEthinksaas vulnerabilities
Recent CVEs affecting thinksaas products. 6 tracked.
thinksaas has 6 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2024-07-21. Highest priority: CVE-2024-40456 (score 55/100).
- CVE-2024-6942 LOW 3.5 DOWNGRADE A vulnerability, which was classified as problematic, was found in ThinkSAAS 3.7.0
- CVE-2024-6941 LOW 3.5 DOWNGRADE A vulnerability, which was classified as problematic, has been found in ThinkSAAS 3.7.0
- CVE-2024-40456 CRITICAL 9.8 DOWNGRADE ThinkSAAS v3.7.0 was discovered to contain a SQL injection vulnerability via the name parameter at \system\act
- CVE-2024-40455 LOW 2.7 DOWNGRADE An arbitrary file deletion vulnerability in ThinkSAAS v3.7 allows attackers to delete arbitrary files via a cr
- CVE-2024-33102 MEDIUM 5.4 DOWNGRADE A stored cross-site scripting (XSS) vulnerability in the component /pubs/counter.php of ThinkSAAS v3.7.0 allow
- CVE-2024-33101 MEDIUM 6.1 DOWNGRADE A stored cross-site scripting (XSS) vulnerability in the component /action/anti.php of ThinkSAAS v3.7.0 allows
FAQ
How do I fix thinksaas 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 thinksaas being exploited right now?
None of the tracked thinksaas CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which thinksaas CVE should I patch first?
CVE-2024-40456 currently ranks highest (55/100): ThinkSAAS v3.7.0 was discovered to contain a SQL injection vulnerability via the name parameter at \system\act.