CVE-2026-1552
BaseFortify
Publication date: 2026-01-29
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sem-cms | semcms | 5.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an SQL injection flaw in SEMCMS version 5.0, specifically in the file SEMCMS_Info.php. It occurs because the 'searchml' parameter is not properly validated or filtered before being used in SQL statements. An attacker can exploit this by injecting malicious SQL code remotely, which allows unauthorized execution of SQL commands on the database. This can lead to unauthorized access, data leakage, data tampering, and potentially full control over the system. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, leakage of sensitive data, data tampering, disruption of services, and potentially full system compromise. This severely impacts system security and business continuity by allowing attackers to execute arbitrary SQL commands remotely without authentication. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'searchml' parameter in the /SEMCMS_Info.php file for SQL injection flaws. Automated tools like sqlmap have been used successfully to confirm exploitation. You can use sqlmap with a command such as: sqlmap -u "http://target/SEMCMS_Info.php" --data="searchml=payload" --risk=3 --level=5 to test for SQL injection. Additionally, Google dorking with the query "inurl:SEMCMS_Info.php" can help identify vulnerable targets on the internet. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'searchml' parameter, and minimizing database user permissions by avoiding high-privilege accounts like 'root' or 'admin' for routine operations. Since no patches or countermeasures have been provided by the vendor, it is also recommended to consider replacing SEMCMS 5.0 with an alternative product. Regular security audits should be conducted to identify and remediate vulnerabilities promptly. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized access, data leakage, and data tampering, it could potentially lead to violations of data protection regulations that require safeguarding sensitive information. Without explicit statements, a direct assessment cannot be made. [1, 2, 3]