CVE-2025-6938
BaseFortify
Publication date: 2025-07-01
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 |
|---|---|---|
| carmelo | simple_pizza_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-6938 is a critical SQL injection vulnerability in the Simple Pizza Ordering System version 1.0, specifically in the /editcus.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, 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 sensitive data, modification or deletion of database records, and disruption of service. Attackers can remotely execute arbitrary SQL commands without authentication, potentially compromising the confidentiality, integrity, and availability of the system. This can result in data breaches, loss of data integrity, and service outages. [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 'id' parameter in the /editcus.php file for SQL injection. Tools like sqlmap can be used to automate detection. For example, running sqlmap against the URL with the vulnerable parameter: sqlmap -u "http://target/editcus.php?id=1" --batch. Additionally, searching for the vulnerable endpoint using Google dorking such as "inurl:editcus.php" can help identify targets. Manual testing can include injecting SQL payloads in the 'id' parameter and observing responses for SQL errors or behavior changes. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product if possible. If replacement is not feasible, implement prepared statements with parameter binding to separate SQL code from user input, enforce strict input validation and filtering on the 'id' parameter, and minimize database user privileges by avoiding high-privilege accounts for routine operations. Conduct regular security audits to detect and address vulnerabilities promptly. [2, 3, 1]