CVE-2025-10400
BaseFortify
Publication date: 2025-09-14
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 |
|---|---|---|
| oretnom23 | food_ordering_management_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-10400 is a critical SQL injection vulnerability in SourceCodester Food Ordering Management System version 1.0, specifically in the file /routers/ticket-message.php. It occurs because the ticket_id parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This lets attackers manipulate backend database queries, potentially accessing, modifying, or deleting data without authorization. The vulnerability can be exploited remotely and requires only a basic user account. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to gain unauthorized access to your database, leading to data leakage, modification, or deletion. It threatens the confidentiality, integrity, and availability of your system. Attackers can disrupt services, compromise sensitive information, and potentially take full control of the affected system. The exploit is publicly available and can be executed remotely, increasing the risk of attack. [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 'ticket_id' parameter in POST requests to the /routers/ticket-message.php file for SQL injection. You can use tools like sqlmap targeting the 'ticket_id' parameter with high risk and level settings. Additionally, Google dorking with the query 'inurl:routers/ticket-message.php' can help identify vulnerable targets. Example sqlmap command: sqlmap -u "http://target/routers/ticket-message.php" --data="ticket_id=1" --risk=3 --level=5 --batch [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection. 2) Applying strict input validation and filtering on the 'ticket_id' parameter to ensure it conforms to expected formats. 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conducting regular security audits to detect and remediate vulnerabilities promptly. Since no patches or fixes are currently available, consider replacing the affected component with an alternative product. [1, 2, 3]