CVE-2024-3816: Sites managed in S@M CMS (Concept Intermedia) might be vulnerable to a blind SQL Injection executed using the

Q: How do I fix CVE-2024-3816?

s\@m cms: upgrade to newer than 3.3. Exact commands for each OS are on this page.

Q: Is CVE-2024-3816 being exploited?

CVE-2024-3816 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-3816 affect?

CVE-2024-3816 affects s\@m cms. Severity is critical (CVSS 9.8). Sites managed in S@M CMS (Concept Intermedia) might be vulnerable to a blind SQL Injection executed using the search bar. Only a part of observed services is vulnerable, but since vendor has not investigated the root problem, it is hard to

Q: How urgent is CVE-2024-3816?

Priority 50/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2024-3816 is a critical-severity flaw (CVSS 9.8) affecting s\@m cms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Sites managed in S@M CMS (Concept Intermedia) might be vulnerable to a blind SQL Injection executed using the search bar. Only a part of observed services is vulnerable, but since vendor has not investigated the root problem, it is hard to determine when the issue appears.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 58%)
CISA exploited list	No
Weakness	CWE-89
Published	2024-06-28
Last modified	2026-06-17

Publisher (CNA): CERT.PL · Vendor: conceptintermedia

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-06-28 13:15 UTCPublished CVE record published
2026-06-17 07:45 UTCUpdated Record last modified

conceptintermedia s\@m cms UPGRADE

Affected: <= 3.3

Fixed in: newer than 3.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy sm-cms || rpm -q sm-cms || sm-cms --version

2. UPGRADE to newer than 3.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sm-cms

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sm-cms

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-3816?

s\@m cms: upgrade to newer than 3.3. Exact commands for each OS are on this page.

Is CVE-2024-3816 being exploited?

CVE-2024-3816 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-3816 affect?

CVE-2024-3816 affects s\@m cms. Severity is critical (CVSS 9.8). Sites managed in S@M CMS (Concept Intermedia) might be vulnerable to a blind SQL Injection executed using the search bar. Only a part of observed services is vulnerable, but since vendor has not investigated the root problem, it is hard to

How urgent is CVE-2024-3816?

Priority 50/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

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

References

← Back to latest CVEs