VulnerabilityPublished 5 Dec 2025

CVE-2025-14091: TrippWasTaken PHP-Guitar-Shop · SQL Injection

Affects TrippWasTaken PHP-Guitar-ShopSource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 22% 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 5 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, 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

Organizations should immediately audit their PHP-Guitar-Shop installations to identify affected versions or commits. Since no official patches are available, implement strict input validation and sanitization on the 'ID' parameter in /product.php, preferably using parameterized queries or prepared statements to prevent SQL injection. Employ Web Application Firewalls (WAFs) with rules targeting SQL injection patterns to provide an additional protective layer. Monitor web server and database logs for suspicious query patterns or repeated failed attempts to exploit the vulnerability. Restrict database user privileges to the minimum necessary to limit the impact of potential exploitation. Consider isolating the e-commerce application in a segmented network zone to reduce lateral movement risks. Engage in proactive threat hunting and update incident response plans to address potential exploitation scenarios. Finally, maintain regular backups of critical data to enable recovery in case of data corruption or deletion.

Description

A weakness has been identified in TrippWasTaken PHP-Guitar-Shop up to 6ce0868889617c1975982aae6df8e49555d0d555. This vulnerability affects unknown code of the file /product.php of the component Product Details Page. Executing manipulation of the argument ID can lead to sql injection. It is possible to launch the attack remotely. The exploit has been made available to the public and could be exploited. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using the PHP-Guitar-Shop platform, this vulnerability poses a significant risk to the confidentiality and integrity of their customer and transactional data. Successful exploitation could lead to unauthorized data disclosure, data tampering, or deletion, undermining customer trust and potentially violating GDPR requirements. Availability impacts, while partial, could disrupt e-commerce services, leading to financial losses and reputational damage. The public availability of exploit code increases the likelihood of attacks, especially against organizations that have not implemented mitigations. Given the widespread use of PHP-based e-commerce solutions in Europe, particularly in countries with mature online retail markets, the threat could affect a broad range of small to medium-sized businesses. The lack of vendor patches and the rolling release model complicate timely remediation, increasing exposure duration. Additionally, attackers could use this vulnerability as a foothold for lateral movement or further compromise within corporate networks.

Summary

CVE-2025-14091 identifies a SQL injection vulnerability in the TrippWasTaken PHP-Guitar-Shop product, affecting the /product.php file responsible for rendering the Product Details Page. The vulnerability stems from insufficient sanitization and validation of the 'ID' parameter, which is used directly in SQL queries. This allows an unauthenticated remote attacker to inject malicious SQL code, potentially extracting, modifying, or deleting data from the backend database. The product follows a rolling release model, making it difficult to pinpoint affected versions beyond the specific commit hash provided. The vendor has not issued any patches or responses, and exploit code has been publicly disclosed, increasing the risk of exploitation. The CVSS 4.0 score of 6.9 reflects a medium severity, with network attack vector, no required privileges or user interaction, and partial impacts on confidentiality, integrity, and availability. The vulnerability does not require authentication or user interaction, making it easier to exploit remotely. The lack of vendor response and patch availability means organizations must implement mitigations independently. This vulnerability could be leveraged to compromise sensitive customer data, disrupt e-commerce operations, or facilitate further attacks within affected environments.

References

Community reviews

Loading reviews…