CVE-2025-0208

6.3 MEDIUM

📋 TL;DR

CVE-2025-0208 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 'tid' parameter in /summary.php. This affects all deployments of this specific e-commerce software version. Attackers can potentially steal sensitive data, modify database contents, or gain unauthorized access.

💻 Affected Systems

Products:
  • code-projects Online Shoe Store
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of version 1.0 are vulnerable; no specific configuration required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to theft of customer PII, payment information, and administrative credentials; potential for full system takeover via SQL injection to RCE chaining.

🟠

Likely Case

Data exfiltration of customer information, order history, and potentially hashed passwords; database manipulation affecting store operations.

🟢

If Mitigated

Limited impact with proper input validation and WAF rules blocking SQL injection patterns; potential for denial of service attempts.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Public exploit available on GitHub gist; simple HTTP request with crafted tid parameter required.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

No official patch available. Consider migrating to alternative e-commerce platforms or implementing custom fixes with parameterized queries.

🔧 Temporary Workarounds

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns targeting /summary.php

Input Validation Filter

all

Add server-side validation to only accept numeric values for tid parameter

🧯 If You Can't Patch

  • Isolate the application behind a reverse proxy with strict input validation
  • Implement database access controls to limit application user permissions

🔍 How to Verify

Check if Vulnerable:

Send a test request to /summary.php?tid=1' OR '1'='1 and check for SQL error responses or unexpected behavior

Check Version:

Check application files for version indicators or README documentation

Verify Fix Applied:

Test with SQL injection payloads and verify they are rejected or sanitized without database errors

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple requests to /summary.php with suspicious tid parameters
  • Database query errors containing single quotes or SQL keywords

Network Indicators:

  • HTTP requests to /summary.php with SQL injection patterns in tid parameter
  • Unusual database connection patterns from web server

SIEM Query:

source="web_logs" AND uri_path="/summary.php" AND (query_string="*tid=*'*" OR query_string="*tid=*%27*")

🔗 References

📤 Share & Export