Skip to main content
VulnerabilityPublished Updated

CVE-2024-46103: SEMCMS · Code Injection

Affects SEMCMSSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubn0zom1z0/SEMCMSpkg:github/n0zom1z0/SEMCMSOther threatsAffected
  • =4.8
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official patch is released, organizations should implement several specific mitigations to reduce risk. First, restrict network access to the SEMCMS_Main.php endpoint using web application firewalls (WAFs) or network-level controls to limit exposure to untrusted sources. Deploy WAF rules specifically designed to detect and block SQL Injection patterns targeting SEMCMS. Conduct thorough input validation and sanitization on all user-supplied data at the application level, employing parameterized queries or prepared statements wherever possible. Monitor application and database logs for unusual query patterns or errors indicative of injection attempts. Consider temporarily disabling or restricting functionality that interacts with SEMCMS_Main.php if feasible. Maintain regular backups of databases to enable recovery in case of compromise. Finally, stay alert for official patches or updates from SEMCMS vendors and prioritize their deployment once available to fully remediate the vulnerability.

Description

SEMCMS 4.8 is vulnerable to SQL Injection via SEMCMS_Main.php.

References

Community reviews

Loading reviews…