Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-15165: SQL Injection in itsourcecode Online Cake Ordering System

0
Medium
VulnerabilityCVE-2025-15165cvecve-2025-15165
Published: Mon Dec 29 2025 (12/29/2025, 01:02:08 UTC)
Source: CVE Database V5
Vendor/Project: itsourcecode
Product: Online Cake Ordering System

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.

AI-Powered Analysis

AILast updated: 12/30/2025, 23:13:24 UTC

Technical Analysis

The vulnerability identified as CVE-2025-15165 affects the itsourcecode Online Cake Ordering System version 1.0. It is an SQL injection vulnerability located in the /updatecustomer.php script, specifically when the 'action=edit' parameter is used and the 'ID' argument is manipulated. This improper input sanitization allows an unauthenticated remote attacker to inject arbitrary SQL commands into the backend database query. The vulnerability can be exploited without any user interaction or privileges, making it accessible to any remote attacker with network access to the web application. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the network attack vector, low complexity, no authentication, and partial impact on confidentiality, integrity, and availability. While no exploits have been reported in the wild, the public disclosure of the vulnerability increases the risk of exploitation by attackers seeking to extract sensitive customer data, modify database records, or disrupt service availability. The affected product is typically deployed by small to medium-sized enterprises in the food ordering and catering industry, which may lack mature security practices. The absence of vendor patches or official remediation guidance necessitates immediate mitigation through secure coding practices such as using parameterized queries, input validation, and deploying web application firewalls to detect and block SQL injection attempts.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality of customer data, including personal and payment information, as well as the integrity of order and customer records. Successful exploitation could lead to unauthorized data disclosure, data manipulation, or denial of service conditions impacting business operations. Small and medium-sized enterprises in the food delivery and catering sectors, which often rely on such online ordering systems, may face reputational damage, regulatory penalties under GDPR for data breaches, and financial losses. The remote and unauthenticated nature of the attack vector increases the likelihood of exploitation, especially in environments with limited security monitoring. Disruption of online ordering services could also affect customer trust and revenue streams. Given the widespread use of e-commerce platforms in Europe, the vulnerability could have a broad impact if left unmitigated.

Mitigation Recommendations

1. Immediate code remediation should be undertaken to replace vulnerable SQL query constructions with parameterized queries or prepared statements to prevent injection. 2. Implement strict input validation and sanitization on all user-supplied parameters, particularly the 'ID' parameter in /updatecustomer.php. 3. Deploy a web application firewall (WAF) configured to detect and block SQL injection patterns targeting this endpoint. 4. Conduct thorough security testing, including automated and manual penetration tests, to verify the absence of injection flaws. 5. Monitor web application logs for suspicious query patterns or repeated failed attempts to exploit the injection point. 6. If patching is not immediately possible, consider isolating the vulnerable system behind network controls or limiting access to trusted IP addresses. 7. Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases. 8. Prepare an incident response plan in case exploitation is detected, including data breach notification procedures compliant with GDPR.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-12-27T23:11:07.040Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 695450b2db813ff03e2bee6c

Added to database: 12/30/2025, 10:22:42 PM

Last enriched: 12/30/2025, 11:13:24 PM

Last updated: 2/7/2026, 10:07:24 PM

Views: 21

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats