CVE-2025-14649
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 |
|---|---|---|
| admerc | online_cake_ordering_system | 1.0 |
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 issue in the itsourcecode Online Cake Ordering System 1.0, specifically in the /cakeshop/supplier.php file. By manipulating the 'supplier' argument, an attacker can inject malicious SQL code. The attack can be performed remotely, and the exploit is publicly available.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute arbitrary SQL commands on the database, potentially leading to unauthorized data access, data modification, or deletion. It can compromise the confidentiality, integrity, and availability of the affected system's data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized database access, data leakage, modification, or deletion, which can compromise the confidentiality, integrity, and availability of sensitive data. Such impacts can lead to non-compliance with data protection standards and regulations like GDPR and HIPAA that require safeguarding personal and sensitive information. Therefore, exploitation of this vulnerability could result in violations of these regulations due to potential unauthorized disclosure or alteration of protected data. [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 '/cakeshop/supplier.php' endpoint for SQL injection via the 'supplier' parameter. Tools like sqlmap can be used to automate detection by sending crafted POST requests to '/cakeshop/insertsupplier.php' with the 'supplier' parameter. Additionally, Google dorking with queries such as 'inurl:cakeshop/supplier.php' can help identify potentially vulnerable targets. Example command using sqlmap: sqlmap -u "http://target.com/cakeshop/supplier.php" --data="supplier=test" --risk=3 --level=5 [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Apply strict input validation and filtering to ensure the 'supplier' parameter conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations. 4) Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. If possible, replace the affected component with a secure alternative. [2, 3]