CVE-2025-15165
Unknown Unknown - Not Provided
SQL Injection in itsourcecode Cake Ordering System /updatecustomer.php

Publication date: 2025-12-29

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability has been found in itsourcecode Online Cake Ordering System 1.0. The impacted element is an unknown function of the file /updatecustomer.php?action=edit. The manipulation of the argument ID leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-29
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-12-29
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
itsourcecode online_cake_ordering_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 in the itsourcecode Online Cake Ordering System 1.0. It occurs in an unknown function within the file /updatecustomer.php?action=edit, where manipulation of the argument ID allows an attacker to inject malicious SQL code. The attack can be performed remotely and the exploit has been publicly disclosed.


How can this vulnerability impact me? :

The vulnerability can allow an attacker to execute arbitrary SQL commands on the database, potentially leading to unauthorized data access, data modification, or deletion. This can compromise the confidentiality, integrity, and availability of the system's data.


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, tampering, and full system compromise. Such unauthorized access and potential data breaches can negatively impact compliance with data protection standards and regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information. Failure to remediate this vulnerability may result in violations of these regulations due to compromised confidentiality and integrity of data. [1, 2, 3]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This SQL injection vulnerability can be detected by testing the vulnerable parameter 'id' in the file /cakeshop/updatecustomer.php with the parameter action=edit. Tools like sqlmap can be used to automate detection by sending crafted POST requests to /cakeshop/updatecustomer1.php targeting the 'id' parameter to check for SQL injection. Example command using sqlmap: sqlmap -u "http://targetsite/cakeshop/updatecustomer.php?action=edit&id=40" --data="id=40" --risk=3 --level=5 --batch. Additionally, monitoring for unusual database queries or unexpected behavior in the application when accessing this endpoint can help detect exploitation attempts. [3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Enforce strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and address vulnerabilities promptly. Since no known countermeasures or patches are currently available, replacing the affected product with an alternative solution is recommended to secure the system and maintain data integrity. [2, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart