CVE-2026-0546
SQL Injection in code-projects CMS search.php Enables Remote Exploit
Publication date: 2026-01-02
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 |
|---|---|---|
| code-projects | content_management_system | 1.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?
CVE-2026-0546 is a SQL injection vulnerability in version 1.0 of the code-projects Content Management System, specifically in the search.php file. The vulnerability occurs because the 'value' parameter in HTTP GET requests is not properly sanitized or validated before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially manipulating the database queries. The flaw corresponds to CWE-89 and can be exploited using various SQL injection techniques such as boolean-based blind, time-based blind, and UNION queries. [1, 2, 3]
How can this vulnerability impact me? :
Successful exploitation of this vulnerability can lead to unauthorized access to the database, data leakage, data tampering, full system compromise, and disruption of services. Because the vulnerability can be exploited remotely without authentication, attackers can easily manipulate the system, compromising confidentiality, integrity, and availability of the affected CMS. [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 'value' parameter in HTTP GET requests to the search.php file for SQL injection. You can use payloads such as boolean-based blind, time-based blind, or UNION query injections. Example payloads include: - Boolean-based blind: value=-8849' OR 8797=8797 # - Time-based blind: value=aaa' AND (SELECT SLEEP(5))-- - UNION query: value=aaa' UNION ALL SELECT NULL,CONCAT(0x717a786b71,0x63636a566151794d656e707268445642736e4b63594858446b5342615769537545516564746b7569,0x7171706271),NULL,NULL,NULL,NULL,NULL # You can also use tools like sqlmap to automate detection by targeting the vulnerable parameter with crafted HTTP GET requests. Additionally, attackers may identify vulnerable targets using Google dorking with queries like "inurl:search.php". [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Replace the affected CMS with an alternative product if possible. - Use prepared statements with parameter binding to separate SQL code from user input. - Implement rigorous input validation and filtering to ensure inputs conform to expected formats. - Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. No known countermeasures or patches are documented, so these steps are critical to protect system security and maintain data integrity. [1, 2, 3]
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, given that the vulnerability allows unauthorized database access, data leakage, and data tampering, it could potentially lead to violations of data protection and privacy regulations by compromising the confidentiality and integrity of sensitive data. Immediate remediation is critical to maintain data security and compliance. [1, 2, 3]