CVE-2026-0565
SQL Injection in code-projects CMS /admin/delete.php Allows Remote Exploits
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-0565 is a SQL injection vulnerability in the Code-projects Content Management System version 1.0, specifically in the /admin/delete.php file. The vulnerability occurs because the 'del' parameter is not properly sanitized or validated before being used in SQL queries. This allows an attacker to inject malicious SQL commands remotely without authentication, potentially manipulating the database in unauthorized ways. The flaw impacts the confidentiality, integrity, and availability of the system, and a public proof-of-concept exploit is available. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and service disruption. Because the attack can be executed remotely without authentication, attackers can manipulate SQL queries to alter or delete data, compromise system integrity, and disrupt availability. The impact includes loss of confidentiality, integrity, and availability of the affected system. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for the vulnerable URL pattern using Google dorking with the query "inurl:admin/delete.php" to identify potentially affected systems. Additionally, exploitation attempts can be detected by monitoring HTTP requests targeting the /admin/delete.php file with the "del" parameter. For example, using sqlmap to test the injection point is effective. An example of a vulnerable request is: GET /cmsphp/admin/delete.php?del=4 HTTP/1.1. A time-based blind SQL injection payload such as `del=4' AND (SELECT 9062 FROM (SELECT(SLEEP(5)))Inwk) AND 'piLZ'='piLZ` can be used to confirm the vulnerability. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected product with an alternative solution, as no known countermeasures exist. Additionally, recommended remediation involves using prepared statements with parameter binding to prevent SQL injection, implementing strict input validation and filtering on the "del" parameter, and limiting database user permissions to the minimum necessary to reduce impact. Avoid using high-privilege accounts for routine database operations. Prompt corrective action is critical to protect system security and data integrity. [1, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in code-projects Content Management System 1.0 can lead to unauthorized access, data leakage, and manipulation of sensitive information, which negatively impacts the confidentiality, integrity, and availability of data. Such impacts can cause non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access and breaches. Therefore, exploitation of this vulnerability could result in violations of these regulations due to compromised data security. [1, 3]