VulnerabilityPublished 28 Aug 2025

CVE-2025-51969: PuneethReddyHC Online Shopping System Advanced · SQL Injection

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.5Medium

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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 impacted component.
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 on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 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 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 or the CVSS exploit maturity 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

To mitigate this vulnerability, organizations should immediately implement input validation and parameterized queries (prepared statements) for the product_id parameter in the product.php page. Avoid directly embedding user input into SQL statements. Employ web application firewalls (WAFs) with rules to detect and block SQL injection attempts targeting the product.php endpoint. Conduct thorough code reviews and security testing (including automated scanning and manual penetration testing) to identify and remediate similar injection flaws. Monitor web server logs for suspicious query strings containing SQL syntax or unusual characters. If possible, restrict access to the product.php page or implement rate limiting to reduce attack surface. Finally, ensure regular backups of the database to enable recovery in case of data tampering.

Description

A SQL Injection vulnerability exists in the product.php page of PuneethReddyHC Online Shopping System Advanced 1.0. This flaw is present in the product_id GET parameter, which is not properly validated before being included in a SQL statement.

Impact

For European organizations using the PuneethReddyHC Online Shopping System Advanced 1.0, this vulnerability poses a risk of unauthorized data disclosure and data integrity compromise. E-commerce platforms typically handle sensitive customer information, including personal details and payment data. While the CVSS vector indicates no direct impact on availability, the confidentiality and integrity breaches could lead to exposure of customer data, loss of trust, and potential regulatory penalties under GDPR. Additionally, attackers could manipulate product information or pricing, causing financial and reputational damage. The lack of authentication requirement means attackers can exploit this vulnerability without credentials, increasing the risk of widespread attacks. Organizations in Europe must be vigilant, especially those relying on this specific shopping system or similar vulnerable components, as exploitation could facilitate further attacks or data breaches.

Summary

CVE-2025-51969 is a medium severity SQL Injection vulnerability identified in the product.php page of the PuneethReddyHC Online Shopping System Advanced 1.0. The vulnerability arises from improper validation of the product_id parameter passed via a GET request. Specifically, the product_id parameter is directly incorporated into a SQL query without adequate sanitization or parameterization, allowing an attacker to inject malicious SQL code. This flaw corresponds to CWE-89, which covers improper neutralization of special elements in SQL commands. Exploiting this vulnerability does not require authentication or user interaction, and can be performed remotely over the network (AV:N). The CVSS 3.1 base score is 6.5, indicating a medium severity impact primarily affecting confidentiality and integrity, but not availability. Successful exploitation could allow an attacker to read unauthorized data from the database or modify data, potentially leading to data leakage or corruption. However, no known exploits are currently reported in the wild, and no patches have been published yet. The vulnerability affects an unspecified version of the PuneethReddyHC Online Shopping System Advanced 1.0, which is an e-commerce platform. Given the nature of the vulnerability, it is likely exploitable by crafting malicious URLs targeting the product.php page with manipulated product_id parameters.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/jairajparyani/CVE-s/blob/main/CVE-2025-51969%20%E2%80%93%20SQL%20Injection%20in%20Online%20Shopping%20System%20Advanced (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Sep 2025, 18:34 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats