CVE-2025-14091
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-05

Last updated on: 2026-04-29

Assigner: VulDB

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-05
Last Modified
2026-04-29
Generated
2026-06-16
AI Q&A
2025-12-10
EPSS Evaluated
2026-06-14
NVD
CVE-2025-14091
EUVD
EUVD-2025-201422
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
trippwastaken php-guitar-shop *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 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.
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

This SQL injection vulnerability allows remote attackers to access and manipulate sensitive data without authentication, potentially leading to unauthorized disclosure and alteration of personal or protected information. Such unauthorized access and data breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding the confidentiality and integrity of sensitive data. Therefore, exploitation of this vulnerability could negatively impact compliance with these common standards and regulations. [1, 2]

Detection Guidance

This vulnerability can be detected by identifying if the /product.php page is accessible and if the 'id' parameter is vulnerable to SQL injection. Attackers can use Google dorking with queries like "inurl:product.php" to find potential targets. To test on your system, you can use tools like curl or sqlmap to send crafted requests to /product.php with manipulated 'id' parameters and observe if SQL errors or unexpected behavior occur. For example, using curl: curl "http://yourtarget/product.php?id=1' OR '1'='1" or using sqlmap: sqlmap -u "http://yourtarget/product.php?id=1" --batch --dbs. These commands help detect if the parameter is vulnerable to SQL injection. [2]

Mitigation Strategies

Immediate mitigation steps include disabling or restricting access to the vulnerable /product.php page if possible, applying input validation and sanitization on the 'id' parameter to prevent SQL injection, and considering replacing the affected product with an alternative since no official patches or mitigations have been published. Additionally, monitoring for suspicious activity and blocking malicious requests targeting the 'id' parameter can help reduce risk until a fix is available. [2]

Executive Summary

This vulnerability is a SQL injection weakness in the TrippWasTaken PHP-Guitar-Shop application, specifically in the /product.php file of the Product Details Page component. By manipulating the 'ID' argument, an attacker can inject malicious SQL code. This can be done remotely without any authentication, making it possible for attackers to exploit the database through crafted requests.

Impact Analysis

Exploiting this vulnerability can allow an attacker to access, modify, or delete data in the application's database. This can lead to unauthorized data disclosure, data corruption, or denial of service. Since the attack can be performed remotely and without authentication, it poses a significant risk to the confidentiality, integrity, and availability of the affected system.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-14091. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart