CVE-2026-1552VulnerabilityPublished 29 Jan 2026Updated 23 Feb 2026

CVE-2026-1552: SEMCMS · SQL Injection

Affects SEMCMSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SEMCMS	Affected =5.0	Fixed in–

AI-suggested

1. Implement strict input validation and sanitization on the 'searchml' parameter to block malicious SQL code. 2. Deploy a Web Application Firewall (WAF) with rules targeting SQL injection patterns to detect and block exploit attempts. 3. Monitor web server and database logs for unusual query patterns or repeated access to /SEMCMS_Info.php with suspicious parameters. 4. Restrict database user permissions to the minimum necessary to limit damage if exploitation occurs. 5. Isolate SEMCMS servers within segmented network zones to reduce lateral movement risk. 6. Engage with the vendor or community for updates and patches, and apply them promptly once available. 7. Consider temporary disabling or restricting access to vulnerable functionality if feasible until a patch is released. 8. Conduct regular security assessments and penetration testing focused on injection vulnerabilities. These steps go beyond generic advice by focusing on specific parameter hardening, monitoring, and network segmentation tailored to this vulnerability.

Description

A security vulnerability has been detected in SEMCMS 5.0. This vulnerability affects unknown code of the file /SEMCMS_Info.php. The manipulation of the argument searchml leads to sql injection. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The SQL injection vulnerability can lead to unauthorized disclosure of sensitive information stored in the database, unauthorized modification or deletion of data, and potential denial of service if database queries are disrupted. This compromises confidentiality, integrity, and availability to varying degrees. Since exploitation requires no authentication and can be performed remotely, attackers can leverage this flaw to gain footholds in affected systems, escalate privileges, or pivot to other internal resources. Organizations using SEMCMS 5.0 may face data breaches, reputational damage, regulatory penalties, and operational disruptions. The absence of a vendor patch and public exploit information increases the urgency for organizations to implement mitigations. The impact is particularly significant for organizations handling sensitive or regulated data through SEMCMS.

Summary

CVE-2026-1552 identifies an SQL injection vulnerability in SEMCMS version 5.0, specifically within the /SEMCMS_Info.php file. The vulnerability arises from improper sanitization of the 'searchml' parameter, which allows an attacker to inject malicious SQL code remotely without requiring authentication or user interaction. This injection can manipulate backend database queries, potentially exposing sensitive data, modifying database contents, or disrupting service availability. The CVSS 4.0 base score is 5.3, reflecting medium severity due to the low attack complexity and no need for privileges, but limited impact on confidentiality, integrity, and availability. The vendor was notified but has not responded or provided a patch, and while public exploit details are available, no active exploitation has been confirmed. The vulnerability affects only SEMCMS 5.0, a content management system whose market penetration is limited but may be critical in certain regions or sectors. The lack of vendor response increases risk, as organizations must rely on defensive measures until a fix is released.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:35 UTC

Technical details

References

Community reviews

Related threats