CVE-2025-14091
BaseFortify
Publication date: 2025-12-05
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| trippwastaken | php-guitar-shop | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
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.
How can this vulnerability impact me? :
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.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
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]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
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]
What immediate steps should I take to mitigate this vulnerability?
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]