CVE-2025-11558VulnerabilityPublished 9 Oct 2025

CVE-2025-11558: code-projects E-Commerce Website · SQL Injection

Affects code-projects E-Commerce WebsiteSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 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-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects E-Commerce Website	Affected =1.0	Fixed in–

AI-suggested

Organizations should immediately audit their use of the code-projects E-Commerce Website version 1.0 and identify any instances of the vulnerable /pages/user_index_search.php component. In the absence of an official patch, developers must implement robust input validation and sanitization for the 'Search' parameter, preferably using parameterized queries or prepared statements to prevent SQL injection. Web application firewalls (WAFs) should be configured to detect and block SQL injection patterns targeting this endpoint. Regular monitoring and analysis of web server and database logs can help identify suspicious query patterns indicative of exploitation attempts. Organizations should also consider isolating the affected application components within segmented network zones to limit potential lateral movement. Conducting penetration testing and code reviews focused on SQL injection vulnerabilities can uncover similar issues. Finally, organizations should maintain an incident response plan tailored to data breaches and web application attacks to respond swiftly if exploitation occurs.

Description

CVE-2025-11558 is a medium-severity SQL injection vulnerability found in version 1.0 of the code-projects E-Commerce Website, specifically in the /pages/user_index_search.php file. The vulnerability arises from improper sanitization of the 'Search' argument, allowing remote attackers to inject malicious SQL commands without authentication or user interaction. Exploitation could lead to partial compromise of confidentiality, integrity, and availability of the backend database. Although no known exploits are currently observed in the wild, the exploit code has been publicly disclosed, increasing the risk of attacks. European organizations using this e-commerce platform are at risk of data breaches, unauthorized data manipulation, and potential service disruption. Mitigation requires immediate input validation, use of prepared statements, and monitoring of web application logs. Countries with higher adoption of this platform or significant e-commerce sectors, such as Germany, France, and the UK, are more likely to be affected. Given the ease of remote exploitation and potential impact, organizations should prioritize patching or applying mitigations promptly.

Impact

For European organizations, exploitation of CVE-2025-11558 could result in unauthorized access to sensitive customer data, including personal and payment information, violating GDPR requirements and potentially incurring heavy fines. Data integrity could be compromised by unauthorized modification of product listings, pricing, or order details, undermining business operations and customer trust. Availability impacts, while limited, could manifest as denial of service through database query manipulation, affecting e-commerce service uptime and revenue. The remote and unauthenticated nature of the vulnerability increases the attack surface, especially for publicly accessible e-commerce websites. Given the public availability of exploit code, attackers may rapidly target vulnerable installations, increasing the risk of data breaches and fraud. European organizations with significant online retail presence or handling large volumes of customer transactions are particularly at risk. The reputational damage and financial losses from such incidents could be substantial, especially in countries with strict data protection enforcement.

Summary

CVE-2025-11558 identifies a SQL injection vulnerability in the code-projects E-Commerce Website version 1.0, located in the /pages/user_index_search.php file. The vulnerability stems from inadequate input validation or sanitization of the 'Search' parameter, which is directly incorporated into SQL queries. This flaw allows an unauthenticated remote attacker to manipulate the SQL query logic by injecting crafted input, potentially extracting sensitive data, modifying database contents, or causing denial of service through query disruption. The vulnerability does not require user interaction or privileges, making it accessible to any remote attacker with network access to the web application. The CVSS 4.0 score of 6.9 reflects a medium severity, considering the attack vector is network-based with low complexity and no authentication required, but with limited impact on confidentiality, integrity, and availability (each rated low). Although no exploits have been observed in the wild, the public disclosure of exploit code increases the likelihood of exploitation attempts. The absence of official patches or vendor advisories necessitates immediate defensive measures by users of this platform. The vulnerability is critical for e-commerce environments where customer data and transaction integrity are paramount. Attackers could leverage this flaw to access customer information, manipulate orders, or disrupt service continuity, leading to reputational damage and regulatory consequences.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Oct 2025, 05:24 UTC

Technical details

References

Community reviews

Related threats