CVE-2025-11513

7.3 HIGH

📋 TL;DR

This SQL injection vulnerability in code-projects E-Commerce Website 1.0 allows attackers to manipulate database queries through the supp_id parameter in /pages/supplier_update.php. Remote attackers can potentially access, modify, or delete sensitive data in the database. All deployments of this specific e-commerce software version are affected.

💻 Affected Systems

Products:
  • code-projects E-Commerce Website
Versions: 1.0
Operating Systems: all
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of version 1.0. The vulnerability is in core application code, not dependent on specific configurations.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, or full system takeover via SQL injection to RCE chaining.

🟠

Likely Case

Unauthorized access to supplier/customer data, manipulation of product/pricing information, or database corruption.

🟢

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: ✅ No
Complexity: LOW

Exploit details are publicly disclosed on GitHub and vuldb. Attack requires access to supplier update functionality.

🛠️ 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

Input Validation Filter

all

Add server-side validation to ensure supp_id parameter contains only numeric values

Modify /pages/supplier_update.php to validate supp_id parameter before processing

WAF Rule Implementation

all

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

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

🧯 If You Can't Patch

  • Block external access to /pages/supplier_update.php via firewall rules or web server configuration
  • Implement database user with minimal permissions (read-only where possible) for the application

🔍 How to Verify

Check if Vulnerable:

Test /pages/supplier_update.php with SQL injection payloads in supp_id parameter (e.g., supp_id=1' OR '1'='1)

Check Version:

Check application files or documentation for version 1.0 references

Verify Fix Applied:

Verify that SQL injection payloads no longer execute and return appropriate error messages or are blocked

📡 Detection & Monitoring

Log Indicators:

  • Unusual database queries from supplier_update.php
  • SQL syntax errors in application logs
  • Multiple failed login attempts followed by supplier_update access

Network Indicators:

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

SIEM Query:

source="web_logs" AND uri="/pages/supplier_update.php" AND (param="*UNION*" OR param="*SELECT*" OR param="*OR*" OR param="*'*" OR param="*--*" OR param="*;*")

🔗 References

📤 Share & Export