s\@m cms vulnerabilities and fixes
Recent CVEs affecting s\@m cms, with upgrade or downgrade steps. 3 tracked.
Also searched as: s\@mcms.
s\@m cms has 3 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 3. Most recent: 2024-06-28. Highest priority: CVE-2024-3816 (score 50/100).
- CVE-2024-3816 CRITICAL 9.8 UPGRADE Sites managed in S@M CMS (Concept Intermedia) might be vulnerable to a blind SQL Injection executed using the
- CVE-2024-3801 MEDIUM 6.1 UPGRADE Sites managed in S@M CMS (Concept Intermedia) might be vulnerable to Reflected XSS via including scripts in on
- CVE-2024-3800 MEDIUM 6.1 UPGRADE Sites managed in S@M CMS (Concept Intermedia) might be vulnerable to Reflected XSS via including scripts in re
FAQ
How do I fix s\@m cms 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 s\@m cms being exploited right now?
None of the tracked s\@m cms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which s\@m cms CVE should I patch first?
CVE-2024-3816 currently ranks highest (50/100): Sites managed in S@M CMS (Concept Intermedia) might be vulnerable to a blind SQL Injection executed using the .