CVE-2026-0565VulnerabilityPublished 2 Jan 2026Updated 23 Feb 2026

CVE-2026-0565: code-projects Content Management System · SQL Injection

Affects code-projects Content Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 2 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-25.

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
code-projects Content Management System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-0565 effectively, organizations should take the following specific actions: 1) Immediately restrict access to the /admin/delete.php endpoint by IP whitelisting or VPN-only access to reduce exposure. 2) Implement strict input validation and sanitization on the 'del' parameter to ensure only expected values are processed, using parameterized queries or prepared statements to prevent SQL injection. 3) Deploy Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting this CMS and parameter. 4) Monitor logs for unusual or suspicious requests to the vulnerable endpoint to detect potential exploitation attempts early. 5) If possible, upgrade to a newer, patched version of the CMS once available, or consider migrating to a more secure platform. 6) Conduct a thorough security audit of the CMS installation and underlying database permissions to minimize the impact of any potential compromise. 7) Educate administrators about the risks and signs of SQL injection attacks to improve incident response readiness. These measures go beyond generic advice by focusing on immediate access restrictions, targeted input validation, and proactive monitoring tailored to this specific vulnerability.

Description

A weakness has been identified in code-projects Content Management System 1.0. This issue affects some unknown processing of the file /admin/delete.php. Executing a manipulation of the argument del can lead to sql injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks.

Impact

The impact of CVE-2026-0565 on organizations worldwide can be significant, especially for those relying on the affected CMS version 1.0. Successful exploitation could allow attackers to execute arbitrary SQL commands, leading to unauthorized access to sensitive data, data corruption, or deletion. This can result in data breaches, loss of data integrity, and potential service disruptions. For organizations handling sensitive or regulated data, this could lead to compliance violations and reputational damage. Since the vulnerability requires no authentication and can be exploited remotely, any publicly accessible installation of the vulnerable CMS is at risk. The availability of public exploit code increases the likelihood of automated attacks and exploitation by less skilled attackers. However, the medium severity score reflects that the overall impact is somewhat limited by the scope of affected systems and the partial impact on confidentiality, integrity, and availability. Organizations with exposed vulnerable CMS instances in critical sectors such as government, healthcare, education, or finance may face higher risks due to the sensitivity of their data and the potential for targeted attacks.

Summary

CVE-2026-0565 is a SQL Injection vulnerability identified in the code-projects Content Management System version 1.0. The vulnerability resides in the /admin/delete.php script, where the 'del' parameter is improperly sanitized or validated, allowing an attacker to inject malicious SQL code. This injection flaw can be exploited remotely without requiring authentication or user interaction, enabling attackers to manipulate backend database queries. Potential consequences include unauthorized data disclosure, data modification, or deletion, and possibly further compromise of the underlying system depending on database privileges. The vulnerability has been assigned a CVSS 4.0 score of 6.9, reflecting a medium severity with network attack vector, low attack complexity, and no privileges or user interaction needed. The exploit code has been publicly released, increasing the likelihood of exploitation attempts. No patches have been officially published yet, and no known active exploits have been reported in the wild. The vulnerability affects only version 1.0 of the CMS, which may be used primarily by small to medium organizations or niche markets. The lack of authentication requirement and remote exploitability make this a significant risk for exposed installations. The vulnerability does not affect the confidentiality, integrity, and availability of the system fully but poses a moderate risk due to partial impact on these security properties.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 23:10 UTC

Technical details

References

Community reviews

Related threats