CVE-2025-6122
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 |
|---|---|---|
| fabian | 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-6122 is a critical SQL injection vulnerability in the Restaurant Order System version 1.0, specifically in the /table.php file. It occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely. [1, 3, 4]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, data leakage of sensitive information, modification or deletion of records, potential full system control by attackers, and service interruptions. Exploitation can be done remotely and may require prior authentication due to default weak credentials in the system. [1, 2, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' parameter in the /table.php file for SQL injection. A common method is to use tools like sqlmap to automate detection. For example, you can run: sqlmap -u "http://target/table.php?id=1" --batch --dbms=mysql to test for SQL injection. Additionally, a proof-of-concept payload for time-based blind SQL injection is: id=1' AND (SELECT 5283 FROM (SELECT(SLEEP(5)))zihG) AND 'OUTg'='OUTg&status=active which can be tested by observing response delays. Vulnerable targets can also be identified using Google dorking with the query: inurl:table.php [3, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'id' parameter, and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Additionally, changing default credentials (which are weak and publicly known) is critical to prevent unauthorized access. Regular security audits should be conducted to detect and fix vulnerabilities promptly. If possible, consider replacing the affected software with an alternative product. [3, 4]