CVE-2025-9749VulnerabilityPublished 31 Aug 2025Updated 2 Sep 2025

CVE-2025-9749: HKritesh009 Grocery List Management Web App · SQL Injection

Affects HKritesh009 Grocery List Management Web AppSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 07:57 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 31 Aug 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.

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. Immediate mitigation should involve implementing input validation and parameterized queries or prepared statements in the /src/update.php file to prevent SQL injection attacks. 2. Conduct a thorough code review of the entire application to identify and remediate any other injection points or insecure coding practices. 3. If possible, deploy a Web Application Firewall (WAF) with rules specifically designed to detect and block SQL injection attempts targeting the 'ID' parameter. 4. Monitor application logs for unusual database query patterns or repeated failed attempts that could indicate exploitation attempts. 5. Engage with the vendor or development team to obtain or request a security patch or update, even if the rolling release model complicates version tracking. 6. Consider isolating or restricting access to the application to trusted networks until a fix is applied. 7. Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases. 8. Regularly back up databases and ensure backups are stored securely to enable recovery in case of data tampering or loss.

Description

A vulnerability was identified in HKritesh009 Grocery List Management Web App up to f491b681eb70d465f445c9a721415c965190f83b. This affects an unknown part of the file /src/update.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available.

Impact

For European organizations using the HKritesh009 Grocery List Management Web App, this vulnerability poses a significant risk to the confidentiality and integrity of their data. Attackers could leverage the SQL injection to extract sensitive user information, alter grocery list data, or disrupt service availability. While the application is niche, organizations relying on it for internal or customer-facing operations could face data breaches or service interruptions. Given the remote and unauthenticated nature of the exploit, attackers can launch attacks at scale, potentially leading to widespread compromise if the app is deployed in multiple environments. The medium severity rating suggests that while the impact is serious, it may not lead to full system takeover without additional vulnerabilities. However, the lack of available patches and the rolling release model complicate timely remediation, increasing exposure duration. European data protection regulations such as GDPR impose strict requirements on data breach prevention and notification, so affected organizations could face regulatory penalties if they fail to address this vulnerability promptly.

Summary

CVE-2025-9749 is a SQL Injection vulnerability identified in the HKritesh009 Grocery List Management Web App, specifically affecting the /src/update.php file. The vulnerability arises from improper sanitization or validation of the 'ID' parameter, which can be manipulated remotely by an unauthenticated attacker to inject malicious SQL queries. This injection flaw allows the attacker to interfere with the application's database queries, potentially leading to unauthorized data access, data modification, or even full database compromise. The vulnerability is exploitable over the network without any authentication or user interaction, increasing the risk of automated exploitation. The CVSS v4.0 base score is 6.9, indicating a medium severity level, with an exploitability rating of 'Proof-of-Concept' (E:P). The vulnerability impacts confidentiality, integrity, and availability to a limited extent (VC:L, VI:L, VA:L), and no scope change is involved. Although no known exploits are reported in the wild yet, the exploit code is publicly available, which could facilitate attacks by malicious actors.

References

Community reviews

Loading reviews…