CVE-2025-0204

6.3 MEDIUM

📋 TL;DR

CVE-2025-0204 is a critical SQL injection vulnerability in code-projects Online Shoe Store 1.0 that allows remote attackers to execute arbitrary SQL commands via the 'id' parameter in /details.php. This affects all deployments of Online Shoe Store 1.0, potentially compromising the entire database. Attackers can steal sensitive data, modify content, or gain unauthorized access.

💻 Affected Systems

Products:
  • code-projects Online Shoe Store
Versions: 1.0
Operating Systems: All operating systems running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of version 1.0 are vulnerable. The vulnerability exists in the default codebase without requiring special configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, authentication bypass, and potential remote code execution if database functions allow it.

🟠

Likely Case

Unauthorized data extraction including user credentials, personal information, and order details, followed by potential privilege escalation.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only allowing data viewing without modification.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable without authentication and affects web applications directly exposed to the internet.
🏢 Internal Only: MEDIUM - While still vulnerable, internal-only deployments have reduced attack surface but remain at risk from insider threats or compromised internal systems.

🎯 Exploit Status

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

Public exploit code is available on GitHub gist, making exploitation trivial for attackers with basic SQL injection knowledge.

🛠️ 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 secure e-commerce platform or implementing manual fixes with parameterized queries and input validation.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add server-side validation to ensure the 'id' parameter contains only numeric values before processing.

Modify /details.php to include: if(!is_numeric($_GET['id'])) { die('Invalid input'); }

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection protection rules to block malicious requests.

🧯 If You Can't Patch

  • Isolate the application behind a reverse proxy with strict input filtering and rate limiting
  • Implement network segmentation to restrict database access from the web server

🔍 How to Verify

Check if Vulnerable:

Test by accessing /details.php?id=1' OR '1'='1 and observing if SQL errors appear or unexpected data is returned.

Check Version:

Check the application's version in its documentation, configuration files, or by examining the source code structure.

Verify Fix Applied:

After implementing fixes, test with the same payloads to ensure proper error handling and no SQL execution.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in web server logs
  • Multiple requests to /details.php with SQL-like payloads in parameters
  • High volume of requests to the same endpoint with varying id parameters

Network Indicators:

  • HTTP requests containing SQL keywords (SELECT, UNION, etc.) in the id parameter
  • Unusual database query patterns from the web server IP

SIEM Query:

source="web_logs" AND uri="/details.php" AND (query="*SELECT*" OR query="*UNION*" OR query="*OR '1'='1*")

🔗 References

📤 Share & Export