CVE-2025-6358
BaseFortify
Publication date: 2025-06-20
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-6358 is a critical SQL injection vulnerability in the Simple Pizza Ordering System version 1.0, specifically in the /saveorder.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This lets attackers manipulate SQL queries, potentially accessing, modifying, or deleting data in the database without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, modification, or deletion of data, and potentially full system compromise. Attackers can disrupt services, manipulate sensitive information, and cause severe risks to system security and business continuity. The exploit can be launched remotely without authentication, making it highly accessible and dangerous. [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 /saveorder.php file for SQL injection flaws. One can use tools like sqlmap to automate detection, for example: sqlmap -u "http://target/saveorder.php" --data="id=1" --batch. Additionally, time-based blind SQL injection techniques (e.g., injecting payloads using MySQL's SLEEP function) can confirm the vulnerability. Google dorking with the query inurl:saveorder.php can help identify vulnerable targets on the network. [2, 3]
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. Regular security audits should be conducted to detect and address vulnerabilities promptly. If possible, replacing the affected component with an alternative product is recommended as no known countermeasures are documented. [2, 3, 1]