VulnerabilityPublished 12 Oct 2025Updated 17 Oct 2025

CVE-2025-11628: jimit105 Project-Online-Shopping-Website · SQL Injection

Affects jimit105 Project-Online-Shopping-WebsiteSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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: High
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
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 12 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 26 Oct 2026.

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

AI-suggested

1. Implement strict input validation and sanitization on all parameters, especially product_code in /delete.php, to prevent SQL injection. 2. Deploy a Web Application Firewall (WAF) with rules specifically targeting SQL injection patterns to detect and block malicious requests. 3. Restrict access to the /delete.php endpoint to only trusted, authenticated users with necessary privileges, and monitor access logs for suspicious activity. 4. Conduct regular code reviews and security testing focusing on injection vulnerabilities, particularly in legacy or rolling release software. 5. Employ database activity monitoring tools to detect anomalous queries indicative of injection attempts. 6. Isolate the database with least privilege principles, ensuring the web application user has minimal rights to reduce potential damage. 7. 8. Maintain an incident response plan to quickly address any detected exploitation attempts. 9. Engage with the vendor or community to track updates or unofficial patches. 10. Educate developers and administrators on secure coding practices and the risks of SQL injection.

Description

A flaw has been found in jimit105 Project-Online-Shopping-Website up to 7d892f442bd8a96dd242dbe2b9bd5ed641e13e64. This affects an unknown function of the file /delete.php of the component Product Inventory Handler. This manipulation of the argument product_code causes sql injection. It is possible to initiate the attack remotely. The exploit has been published and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, especially those operating e-commerce platforms using the Project-Online-Shopping-Website software, this vulnerability poses a risk of unauthorized data manipulation, including deletion or alteration of product inventory information. This can lead to financial losses, reputational damage, and disruption of business operations. The partial compromise of confidentiality could expose sensitive product or customer data, potentially violating GDPR and other data protection regulations. The requirement for high privileges limits exploitation to insiders or compromised accounts, but the ease of remote exploitation without user interaction increases the threat surface. Organizations relying on this software without timely patching or mitigation may face targeted attacks aiming to disrupt sales or steal competitive information. The lack of vendor response and patch availability increases the urgency for organizations to implement compensating controls. Additionally, the rolling release model complicates vulnerability management and increases the risk of unnoticed exposure.

Summary

CVE-2025-11628 identifies a SQL injection vulnerability in the Project-Online-Shopping-Website developed by jimit105, affecting the /delete.php script in the Product Inventory Handler component. The vulnerability is triggered by manipulation of the product_code parameter, which is not properly sanitized before being used in SQL queries. This allows an attacker with high privileges to remotely inject malicious SQL code, potentially leading to unauthorized data access, modification, or deletion. The vulnerability does not require user interaction but does require the attacker to have some level of privileges (PR:H), which suggests that exploitation is limited to authenticated users with elevated rights. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no user interaction (UI:N), and partial impacts on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). The vendor employs a rolling release model, complicating version tracking and patch management, and has not responded to vulnerability reports, leaving affected users without official remediation. Although no known exploits are currently observed in the wild, the public availability of exploit code increases the risk of future attacks. The vulnerability primarily threatens the integrity and confidentiality of the product inventory data and could disrupt e-commerce operations by unauthorized deletion or alteration of product records.

References

Community reviews

Loading reviews…