CVE-2025-15409VulnerabilityPublished 1 Jan 2026Updated 23 Feb 2026

CVE-2025-15409: code-projects Online Guitar Store · SQL Injection

Affects code-projects Online Guitar StoreSource 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 36% 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 1 Jan 2026
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 Online Guitar Store	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2025-15409, organizations should immediately restrict access to the /admin/Delete_product.php endpoint using network-level controls such as IP whitelisting or VPN access to limit exposure. Implement strict input validation and sanitization on the 'del_pro' parameter, ensuring only valid product identifiers are accepted. Refactor the code to use parameterized queries or prepared statements to prevent SQL injection. Conduct a thorough code review of all administrative modules to identify and remediate similar vulnerabilities. If possible, isolate the database with least privilege access, ensuring the web application account cannot perform destructive operations beyond its scope. Monitor logs for suspicious activity targeting the vulnerable endpoint. Since no official patches are available, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts. Finally, plan for an update or migration to a secure version of the software once available.

Description

A vulnerability was determined in code-projects Online Guitar Store 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/Delete_product.php. Executing a manipulation of the argument del_pro can lead to sql injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized.

Impact

The SQL injection vulnerability in the Online Guitar Store can lead to unauthorized data access, data manipulation, or partial denial of service. Attackers exploiting this flaw could retrieve sensitive customer or product information, modify or delete database records, and potentially escalate attacks to compromise the underlying server or network. The impact on confidentiality, integrity, and availability is limited but non-negligible, as attackers can influence database content and access. For organizations, this could result in data breaches, loss of customer trust, regulatory penalties, and operational disruptions. Since the vulnerability is remotely exploitable without authentication, any exposed instance of the affected software is at risk. The lack of known active exploits currently reduces immediate threat but does not eliminate the risk, especially after public disclosure. Organizations relying on this software for e-commerce operations face reputational damage and financial loss if exploited.

Summary

CVE-2025-15409 identifies a SQL injection vulnerability in the code-projects Online Guitar Store version 1.0, specifically within the /admin/Delete_product.php script. The vulnerability stems from inadequate input validation of the 'del_pro' parameter, which is used to specify products for deletion. An attacker can remotely craft malicious input to manipulate the underlying SQL query executed by the application, potentially allowing unauthorized access to or modification of the database. The vulnerability requires no authentication or user interaction, making it accessible to any remote attacker aware of the flaw. The CVSS 4.0 base score of 6.9 reflects a medium severity, considering the network attack vector, low complexity, and no privileges or user interaction needed, but limited impact on confidentiality, integrity, and availability (each rated low). Although no exploits have been observed in the wild, the public disclosure increases the risk of exploitation. The absence of patches or vendor-provided fixes necessitates that users implement immediate mitigations. The vulnerability could allow attackers to extract sensitive data, alter or delete records, or disrupt service availability by injecting malicious SQL commands. This threat highlights the critical need for secure coding practices, especially in administrative modules that control data deletion or modification.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:57 UTC

Technical details

References

Community reviews

Related threats