CVE-2025-11597: code-projects E-Commerce Website · SQL Injection
Affects code-projects E-Commerce WebsiteSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 11 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| code-projects E-Commerce Website | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-11597, organizations should immediately implement strict input validation on the prod_id parameter to ensure only expected data types and values are accepted. Refactoring the affected code to use parameterized queries or prepared statements will prevent SQL injection by separating code from data. If source code modification is not immediately possible, deploying a Web Application Firewall (WAF) with specific rules to detect and block SQL injection attempts targeting prod_id can provide temporary protection. Organizations should audit database user privileges to ensure the web application operates with the least privilege necessary, limiting potential damage from exploitation. Regular monitoring of database logs and web server logs for suspicious queries or anomalies related to product_add_qty.php is recommended. Additionally, organizations should track vendor communications for official patches or updates and apply them promptly once available. Conducting security awareness training for developers on secure coding practices can prevent similar vulnerabilities in future releases. Finally, organizations should prepare incident response plans to quickly address any exploitation attempts.
Description
A vulnerability was identified in code-projects E-Commerce Website 1.0. The impacted element is an unknown function of the file /pages/product_add_qty.php. The manipulation of the argument prod_id leads to sql injection. The attack is possible to be carried out remotely. The exploit is publicly available and might be used.