CVE-2025-6362
BaseFortify
Publication date: 2025-06-20
Last updated on: 2025-06-26
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
How can this vulnerability impact me? :
This vulnerability can allow attackers to gain unauthorized access to the database, potentially exposing sensitive information, modifying or deleting data, disrupting services, and possibly gaining full control over the system. Exploitation does not require authentication, increasing the risk of remote attacks and significant impact on data integrity and system availability. [1, 2, 3]
Can you explain this vulnerability to me?
CVE-2025-6362 is a critical SQL injection vulnerability in the Simple Pizza Ordering System version 1.0, specifically in the /editpro.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized database access, data leakage, modification, or deletion. The attack can be performed remotely without authentication. [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 /editpro.php file for SQL injection. Commands using sqlmap can be employed to automate detection, for example: sqlmap -u "http://<target>/editpro.php?id=1" --batch. Manual testing can include injecting payloads such as 'id=10 AND 3509=3509' for boolean-based blind SQL injection or 'id=10 AND (SELECT SLEEP(5))' for time-based blind SQL injection to observe response delays. Additionally, searching for the vulnerable endpoint using Google dorking with the query "inurl:editpro.php" can help identify affected targets. [2, 3]
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 by separating SQL code from user input. 2) Applying strict input validation and filtering to ensure the 'id' parameter only accepts expected formats. 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for application operations. 4) Conducting regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, replacing the affected software with a secure alternative is recommended. [1, 2, 3]