CVE-2025-6124
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-6124 is a critical SQL injection vulnerability in version 1.0 of the Restaurant Order System, specifically in the /tablelow.php file. The vulnerability occurs because the application improperly handles the 'id' parameter from user input without proper sanitization or validation. This allows attackers to inject malicious SQL code into database queries, enabling unauthorized operations such as retrieving, modifying, or deleting data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact system security by allowing attackers to perform unauthorized database access, extract sensitive information, modify or delete records, and potentially disrupt services. Exploitation requires no authentication and can be done remotely, leading to compromised confidentiality, integrity, and availability of the system. Attackers may gain full control over the affected system, causing significant business and operational risks. [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 /tablelow.php file for injection flaws. One method is to perform a time-based blind SQL injection test using a payload such as: id=2' AND (SELECT 6026 FROM (SELECT(SLEEP(5)))hUZz) AND 'AmNW'='AmNW. This can be done with tools like sqlmap targeting the vulnerable URL with POST data containing the 'id' parameter. Additionally, attackers may be identified by scanning for the URL pattern using Google dorking with the query "inurl:tablelow.php" to find potentially vulnerable instances. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with an alternative product if possible, as no known countermeasures are documented. 2) Implementing prepared statements with parameter binding to prevent SQL injection. 3) Enforcing 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 routine operations. 5) Conducting regular security audits of code and systems to detect and fix vulnerabilities promptly. [2, 3]