CVE-2025-6357
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-6357 is a critical SQL injection vulnerability in the Simple Pizza Ordering System version 1.0, specifically in the /paymentportal.php file. It occurs because the 'person' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code remotely without authentication. This flaw enables attackers to manipulate SQL queries, potentially accessing, modifying, or deleting data in the underlying database. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to sensitive data, data modification, deletion of records, and potentially full control over the affected system. Since no authentication is required and the attack can be launched remotely, it poses a severe risk to data confidentiality, integrity, and availability. [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 'person' parameter in the /paymentportal.php file for SQL injection. One method is to use time-based blind SQL injection payloads, such as sending a POST request with the parameter: person=11111' AND (SELECT 8679 FROM (SELECT(SLEEP(5)))YpyN) AND 'tvxJ'='tvxJ to observe if the response is delayed, indicating vulnerability. Additionally, automated tools like sqlmap can be used to detect and exploit this SQL injection vulnerability. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering on the 'person' parameter, and limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. Regular security audits of code and systems are also recommended. If possible, replacing the affected component with an alternative product is suggested as no known countermeasures are documented. [2, 3]