CVE-2025-11420

7.3

code-projects · E-Commerce Website

A SQL injection vulnerability in the E-Commerce Website allows remote attackers to manipulate the order_id argument within the edit_order_details.php file.

Executive summary

A critical SQL injection vulnerability in code-projects E-Commerce Website 1.0 allows for unauthenticated remote data manipulation and potential database compromise.

Vulnerability

This vulnerability is a SQL injection (CWE-89) flaw located in the /pages/edit_order_details.php file. An unauthenticated attacker can supply malicious input to the order_id parameter to execute unauthorized database queries.

Business impact

Successful exploitation of this flaw could allow an attacker to read, modify, or delete sensitive order information stored in the backend database. Given the CVSS score of 7.3, this represents a significant risk to data integrity and confidentiality for organizations using this software. Unauthorized access to e-commerce records may also lead to severe reputational damage and regulatory non-compliance.

Remediation

Immediate Action: Since no official patch is currently available, administrators should restrict network access to the affected directory or disable the vulnerable component until a security update is released by the vendor.

Proactive Monitoring: Review web server access logs for suspicious patterns in the order_id parameter, specifically looking for common SQL injection keywords like UNION, SELECT, or comment characters.

Compensating Controls: Deploy a Web Application Firewall (WAF) with specific rules designed to inspect and filter input for SQL injection payloads targeting the /pages/edit_order_details.php endpoint.

Exploitation status

Public Exploit Available: Yes, a public proof-of-concept exists as documented in the GitHub issue referenced by the CVE record.

Analyst recommendation

Given the availability of a public proof-of-concept and the ease of exploitation, this vulnerability poses a clear and present danger to affected systems. Organizations must prioritize the implementation of WAF rules or network-level restrictions to block access to the vulnerable script. Monitor vendor channels closely for the release of an official patch and apply it immediately upon availability.

More code-projects CVEs

Sources

Originally found and disclosed by DuXinxing (VulDB User), per the CVE Program record.