CVE-2025-11509VulnerabilityPublished 8 Oct 2025Updated 14 Oct 2025

CVE-2025-11509: 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 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

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:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 8 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

European organizations should immediately audit their use of the code-projects E-Commerce Website to identify any instances of version 1.0. Since no official patches are currently available, organizations should implement the following mitigations: 1) Apply strict input validation and sanitization on the prod_name parameter, ensuring only expected characters and formats are accepted. 2) Refactor the vulnerable code to use parameterized SQL queries or prepared statements to eliminate direct concatenation of user input into SQL commands. 3) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the prod_name parameter. 4) Monitor database logs and web server logs for unusual query patterns or error messages indicative of SQL injection attempts. 5) Restrict database user privileges to the minimum necessary to limit the impact of a successful injection. 6) Conduct regular security assessments and code reviews to identify similar vulnerabilities. 7) Plan for an upgrade or patch deployment as soon as the vendor releases a fix. These steps will help reduce the risk of exploitation and protect sensitive data.

Description

A vulnerability was detected in code-projects E-Commerce Website 1.0. This impacts an unknown function of the file /pages/product_add.php. Performing manipulation of the argument prod_name results in sql injection. The attack may be initiated remotely. The exploit is now public and may be used.

Impact

For European organizations operating or relying on the affected e-commerce platform, this vulnerability poses a risk of unauthorized access to customer data, including personal and payment information, which could lead to data breaches and regulatory non-compliance under GDPR. The integrity of product data and transactional records could also be compromised, potentially disrupting business operations and damaging reputation. Although the vulnerability does not require authentication, the scope is limited to installations of version 1.0 of the code-projects E-Commerce Website, which may reduce the overall exposure. However, given the critical nature of e-commerce platforms in Europe’s digital economy, even limited exploitation could have significant financial and operational consequences. The public availability of exploit code increases the urgency for mitigation. Additionally, attackers could leverage this vulnerability as a foothold for further network intrusion or lateral movement within affected organizations. The medium severity rating reflects a balance between ease of exploitation and limited but meaningful impact on confidentiality, integrity, and availability.

Summary

CVE-2025-11509 is a SQL injection vulnerability identified in version 1.0 of the code-projects E-Commerce Website, specifically within the /pages/product_add.php script. The vulnerability arises from improper sanitization of the prod_name parameter, which allows an attacker to inject malicious SQL code remotely without requiring authentication or user interaction. This flaw enables attackers to manipulate backend database queries, potentially leading to unauthorized data retrieval, data modification, or even complete database compromise depending on the database privileges. The vulnerability has been assigned a CVSS 4.0 score of 5.3, indicating a medium severity level. The attack vector is network-based with low attack complexity, no privileges required, and no user interaction needed. The impact on confidentiality, integrity, and availability is low to limited but still significant for sensitive e-commerce data. Although no known exploits have been observed in the wild, the public availability of exploit code increases the likelihood of exploitation attempts. The vulnerability affects only version 1.0 of the product, and no official patches have been linked yet. The lack of input validation and use of unsafe SQL query construction methods are the root causes. This vulnerability highlights the importance of secure coding practices such as parameterized queries and rigorous input validation in web applications handling sensitive data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Oct 2025, 01:03 UTC

Technical details

References

Community reviews

Related threats