CVE-2025-15074
SQL Injection in itsourcecode Frozen Foods Ordering System
Publication date: 2025-12-25
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_frozen_foods_ordering_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-15074 is a critical SQL injection vulnerability in version 1.0 of the Online Frozen Foods Ordering System, specifically in the file /customer_details.php. The vulnerability occurs because the application improperly handles user input from the 'first_name' parameter, incorporating it directly into SQL queries without proper sanitization or validation. This flaw allows remote attackers to inject malicious SQL code, enabling unauthorized access to the database, data leakage, modification, deletion, and potentially full system compromise or service disruption. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the underlying database, allowing attackers to retrieve sensitive information, modify or delete data, and disrupt system availability. This can result in data breaches, loss of data integrity, service interruptions, and potentially full system compromise, severely impacting business continuity and security. [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 'first_name' in the /customer_details.php file for injection flaws. Tools like sqlmap can be used to automate detection by sending crafted HTTP GET requests with manipulated 'first_name' parameters to observe if SQL injection is possible. Additionally, attackers may be identified by monitoring for HTTP requests targeting /customer_details.php with suspicious or malformed 'first_name' values. Google dorking with the query inurl:customer_details.php can help identify vulnerable targets externally. Example command using sqlmap: sqlmap -u "http://targetsite/frozenfoodssystem/customer_details.php?first_name=TEST" --batch --dbs [1, 3]
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 on the 'first_name' parameter to ensure only expected data formats are accepted. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. Since no official patches or fixes are available, consider replacing the affected product with a secure alternative if possible. [1, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized access, modification, and leakage of sensitive data, it could potentially lead to non-compliance with data protection regulations that require safeguarding personal and sensitive information. [1, 2, 3]