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

Publication date: 2025-12-29

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was determined in itsourcecode Online Cake Ordering System 1.0. This impacts an unknown function of the file /detailtransac.php. This manipulation of the argument ID causes sql injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-29
Last Modified
2026-04-29
Generated
2026-05-06
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, specifically in the /detailtransac.php file. By manipulating the ID argument, an attacker can inject malicious SQL code. This vulnerability can be exploited remotely and the exploit has been publicly disclosed.


How can this vulnerability impact me? :

The vulnerability allows remote attackers to perform SQL injection, which can lead to unauthorized access to or modification of the database. This can result in data leakage, data corruption, or other malicious actions affecting the integrity, confidentiality, and availability of the system.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows unauthorized access, modification, and deletion of sensitive data through SQL injection, which can lead to breaches of confidentiality, integrity, and availability of data. Such breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information. Therefore, exploitation of this vulnerability could cause violations of these standards by exposing or altering protected data without authorization. [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 'id' parameter in the /detailtransac.php file for injectable payloads. Common detection methods include using SQL injection testing tools like sqlmap to automate detection and exploitation attempts. Example commands include using sqlmap with the URL parameter, such as: sqlmap -u "http://targetsite/cakeshop/detailtransac.php?id=1" --batch --dbs. Additionally, manual testing can be done using Boolean-based blind injection payloads (e.g., id=1 AND 1=1 vs id=1 AND 1=2), error-based injections, time-based injections (e.g., id=1 AND SLEEP(5)), or UNION-based injections to check for SQL errors or delays indicating vulnerability. Attackers also use Google dorking with queries like "inurl:detailtransac.php" to identify potentially vulnerable targets. [1, 3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include: 1) Replacing the affected product with an alternative solution if possible, as no known patches are documented. 2) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 3) Applying strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. 4) Minimizing database user permissions by avoiding use of high-privilege accounts for the application database connection. 5) Conducting regular security audits to detect and remediate vulnerabilities promptly. These steps help protect system security and maintain data integrity. [1, 3, 2]


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