CVE-2025-14650
BaseFortify
Publication date: 2025-12-14
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 |
|---|---|---|
| facebook-adrianmercurio | online_cake_ordering_system | 1.0 |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a flaw in the itsourcecode Online Cake Ordering System 1.0, specifically in the /cakeshop/product.php file. It allows an attacker to manipulate the 'Product' argument to perform SQL injection, which means they can execute unauthorized SQL commands on the database remotely.
How can this vulnerability impact me? :
The vulnerability can allow remote attackers to execute SQL injection attacks, potentially leading to unauthorized access, modification, or deletion of data within the system's database. This can compromise the integrity, confidentiality, and availability of the data and the application.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access to sensitive data through SQL injection, which can lead to data leakage, modification, or deletion. Such unauthorized access and potential compromise of data confidentiality and integrity can result in non-compliance with data protection regulations like GDPR and HIPAA, which mandate strict controls over personal and sensitive information. Therefore, this vulnerability poses a risk to compliance with these common standards and regulations. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'product' parameter in POST requests to /cakeshop/product.php or /cakeshop/insertproduct.php for SQL injection. A common method is to use tools like sqlmap to automate detection. For example, using sqlmap targeting the POST request with the 'product' parameter can confirm the injection point. A proof-of-concept payload causing a time delay is: product=123' AND (SELECT 8572 FROM (SELECT(SLEEP(5)))XqBh) AND 'IZqn'='IZqn. Additionally, Google dorking with queries like 'inurl:cakeshop/product.php' can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimize database user permissions by avoiding high-privilege accounts for application database connections. 4) Conduct regular security audits to detect and fix vulnerabilities promptly. If possible, consider replacing the affected product with an alternative solution. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'product' parameter in the /cakeshop/product.php file for SQL injection. A proof-of-concept payload uses a time-based blind SQL injection, such as: product=123' AND (SELECT 8572 FROM (SELECT(SLEEP(5)))XqBh) AND 'IZqn'='IZqn. You can use tools like sqlmap to automate detection by targeting POST requests to /cakeshop/insertproduct.php with the 'product' parameter. Additionally, vulnerable targets can be identified using Google dorking with queries like: inurl:cakeshop/product.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimizing database user permissions by avoiding high-privilege accounts for application database connections. 4) Conducting regular security audits to detect and fix vulnerabilities promptly. If possible, consider replacing the affected product with an alternative solution. [2, 3]