CVE-2025-6123
BaseFortify
Publication date: 2025-06-16
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 |
|---|---|---|
| carmelogarcia | restaurant_order_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-6123 is a critical SQL injection vulnerability in version 1.0 of the Restaurant Order System, specifically in the /payment.php file. The vulnerability occurs because the application uses the 'tabidNoti' parameter directly in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely, enabling unauthorized database operations such as data leakage, modification, or deletion. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data modification or deletion, and potential full system compromise or service disruption. Since it can be exploited remotely without authentication, attackers can manipulate the database, affecting the confidentiality, integrity, and availability of the system. [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 'tabidNoti' parameter in the /payment.php file for SQL injection. A time-based blind SQL injection test can be performed using payloads such as: tabidNoti=3' AND (SELECT 4861 FROM (SELECT(SLEEP(5)))MeaC) AND 'GnDy'='GnDy. Tools like sqlmap can be used to automate detection of this SQL injection vulnerability. Additionally, searching for the vulnerable endpoint using Google dorking with queries like "inurl:payment.php" can help identify targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats. 3) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. 4) Conducting regular security audits of code and systems to detect and address vulnerabilities promptly. If possible, replacing the affected software with an alternative product is recommended as no known mitigations have been published. [2, 3]