CVE-2026-0567
SQL Injection in code-projects CMS /pages.php Allows 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-0567 is a SQL injection vulnerability in the Code-projects Content Management System version 1.0, specifically in the file pages.php. The vulnerability occurs because the 'id' parameter in HTTP GET requests is directly used in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely without authentication, potentially executing unauthorized SQL commands. Types of SQL injection confirmed include boolean-based blind, time-based blind, and UNION query injections. [1, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and denial of service. Attackers can manipulate the 'id' parameter to execute unauthorized SQL commands, potentially gaining control over the system and disrupting services. No authentication is required to exploit this vulnerability, making it highly accessible to attackers. [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 'id' parameter in HTTP GET requests to the /pages.php file for SQL injection. Tools like sqlmap can be used to automate detection with payloads such as boolean-based blind injection (e.g., id=0' AND 2683=2683 AND 'BXVy'='BXVy), time-based blind injection using MySQL's SLEEP() function (e.g., id=0' AND (SELECT 9293 FROM (SELECT(SLEEP(5)))WPCQ) AND 'YrBl'='YrBl), or UNION query injection (e.g., id=0' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,NULL,CONCAT(...)-- -). Additionally, vulnerable targets can be identified using Google dorking with queries like "inurl:pages.php" to find instances of the affected CMS. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include using prepared statements with parameter binding to separate SQL code from user input, implementing strict input validation and filtering to ensure inputs conform to expected formats, and limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. If possible, replacing the affected product with an alternative is also suggested. [1, 2]