CVE-2025-6359
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-6359 is a critical SQL injection vulnerability in the Simple Pizza Ordering System version 1.0, specifically in the /cashconfirm.php file. It occurs because the 'transactioncode' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized access to the database, data leakage, modification, or deletion. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can allow attackers to gain unauthorized access to your database, retrieve sensitive information, modify or delete data, and potentially disrupt system operations. Since the attack can be performed remotely without authentication, it poses a serious risk to system security and business continuity. [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 'transactioncode' parameter in the /cashconfirm.php file for SQL injection. Proof-of-concept testing has been performed using the sqlmap tool targeting the vulnerable URL, for example: sqlmap -u "http://<target>/cashconfirm.php" --data="transactioncode=1" --risk=3 --level=5. Additionally, attackers may use Boolean-based blind SQL injection, time-based blind SQL injection (using MySQL SLEEP()), or UNION-based SQL injection payloads to test for the flaw. Network detection can also involve monitoring for suspicious HTTP POST requests to /cashconfirm.php with unusual or crafted 'transactioncode' values. Google dorking with inurl:cashconfirm.php can help identify vulnerable targets externally. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering on the 'transactioncode' parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts for the application database connection. 4) Replace the affected component with an alternative product if possible. 5) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. [2, 3]