CVE-2026-0567

7.3 HIGH

📋 TL;DR

This SQL injection vulnerability in code-projects Content Management System 1.0 allows attackers to manipulate database queries through the /pages.php file's ID parameter. Remote attackers can potentially read, modify, or delete database content. All installations of this specific CMS version are affected.

💻 Affected Systems

Products:
  • code-projects Content Management System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects the specific 1.0 version of this CMS. The vulnerability is in the /pages.php file.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, and potential remote code execution via database functions.

🟠

Likely Case

Data exfiltration, authentication bypass, privilege escalation, and database manipulation.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only error messages or partial data exposure.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Public exploit available on GitHub. SQL injection via ID parameter manipulation is straightforward for attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://code-projects.org/

Restart Required: No

Instructions:

No official patch available. Consider migrating to a different CMS or implementing workarounds.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add parameterized queries or input validation to /pages.php to sanitize the ID parameter.

Edit /pages.php to implement prepared statements with parameterized queries

Web Application Firewall Rules

all

Implement WAF rules to block SQL injection patterns targeting the /pages.php endpoint.

Add WAF rule: Block requests to /pages.php with SQL injection patterns in parameters

🧯 If You Can't Patch

  • Isolate the CMS instance behind a reverse proxy with strict input filtering
  • Implement network segmentation to limit database access from the web server

🔍 How to Verify

Check if Vulnerable:

Test /pages.php with SQL injection payloads in the ID parameter (e.g., pages.php?id=1' OR '1'='1)

Check Version:

Check CMS version in configuration files or admin panel

Verify Fix Applied:

Test with the same payloads and verify no SQL errors or unexpected behavior occurs

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in web server logs
  • Multiple requests to /pages.php with special characters in ID parameter
  • Database error messages containing SQL syntax

Network Indicators:

  • HTTP requests to /pages.php with SQL keywords in parameters
  • Unusual database traffic patterns from web server

SIEM Query:

source="web_logs" AND uri="/pages.php" AND (param="id" AND value MATCH "[';]|UNION|SELECT|INSERT|UPDATE|DELETE|DROP|OR 1=1")

🔗 References

📤 Share & Export