CVE-2025-15166
SQL Injection in itsourcecode Cake Ordering System /updatesupplier.php
Publication date: 2025-12-29
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 |
|---|---|---|
| itsourcecode | 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 found in the itsourcecode Online Cake Ordering System 1.0, specifically in the /updatesupplier.php?action=edit file. By manipulating the 'ID' argument, an attacker can inject malicious SQL code. The attack can be performed remotely and the exploit has been made public.
How can this vulnerability impact me? :
The SQL injection vulnerability can allow an attacker to access, modify, or delete data in the database without authorization. This can lead to data breaches, loss of data integrity, and potentially full compromise of the affected system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, modification, or deletion of sensitive data through SQL injection, which can lead to breaches of data confidentiality and integrity. Such breaches may result in non-compliance with data protection regulations like GDPR and HIPAA that require safeguarding personal and sensitive information. Therefore, this vulnerability poses a risk to compliance with these common standards and regulations by potentially exposing 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/updatesupplier.php endpoint with the parameters action=edit and id=1 for SQL injection. Tools like sqlmap can be used to automate detection by sending crafted POST requests to this URL to check for SQL injection flaws. For example, a command using sqlmap could be: sqlmap -u "http://targetsite/cakeshop/updatesupplier.php?action=edit" --data="id=1" --risk=3 --level=5 --batch. This will test the id parameter for SQL injection vulnerabilities. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implement strict input validation and filtering to ensure the 'id' parameter only accepts expected formats. 3) Limit database user permissions to the minimum necessary, avoiding high-privilege accounts 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. [1, 2]