CVE-2026-0565

7.3

code-projects · Content Management System

A SQL injection vulnerability in code-projects Content Management System 1.0 allows remote unauthenticated attackers to manipulate the del argument in /admin/delete.php.

Executive summary

A critical SQL injection vulnerability in code-projects Content Management System 1.0 permits remote unauthenticated attackers to execute unauthorized database queries.

Vulnerability

This vulnerability is a SQL injection flaw (CWE-89) located in the /admin/delete.php file. An unauthenticated attacker can exploit this by manipulating the del parameter to execute arbitrary SQL commands.

Business impact

The ability for an unauthenticated attacker to inject SQL commands poses a severe risk to data integrity and confidentiality. Successful exploitation could lead to unauthorized access to the underlying database, potentially resulting in the exposure of sensitive user information or full system compromise. With a CVSS score of 7.3, this high-severity flaw requires immediate attention to prevent malicious data manipulation or extraction.

Remediation

Immediate Action: As no official patch is currently available, administrators should immediately restrict access to the /admin/delete.php endpoint or disable the affected functionality.

Proactive Monitoring: Review web server access logs for anomalous requests containing SQL syntax or unusual patterns targeting the /admin/delete.php file.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SQL injection attempts directed at the identified vulnerable endpoint.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists via the technical write-up on GitHub (https://github.com/Limingqian123/CVE/issues/12).

Analyst recommendation

Given the availability of a public proof-of-concept and the ease of exploitation, this vulnerability poses a significant risk to affected installations. Administrators must prioritize the implementation of compensating controls or network-level restrictions immediately, as an official vendor patch is currently missing. Failure to mitigate this exposure may lead to unauthorized database access and potential system compromise.

More code-projects CVEs all →

History

  1. Disclosed CVE record published
  2. Published in the daily brief high section, carried in 2 daily briefs, Jan 3 to Jan 4
  3. Analyst report written

Sources

Originally found and disclosed by L0ser (VulDB User), per the CVE Program record.