CVE-2025-6361
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
Can you explain this vulnerability to me?
CVE-2025-6361 is a critical SQL injection vulnerability in the Simple Pizza Ordering System version 1.0, specifically in the /adds.php file. The vulnerability occurs because the 'userid' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can be exploited remotely without authentication, enabling attackers to manipulate database queries, potentially accessing, modifying, or deleting sensitive data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to the database, allowing attackers to retrieve sensitive information, modify or delete data, and potentially gain full control over the system. It can also cause service disruption. Since exploitation requires no authentication and can be done remotely, it poses a significant 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 'userid' parameter in the /adds.php file for SQL injection. A proof-of-concept involves using a time-based blind SQL injection payload such as: userid=2' AND (SELECT 9979 FROM (SELECT(SLEEP(5)))SgMe)-- hQaS, which causes a delay in the database response. Tools like sqlmap can be used to automate detection by targeting the vulnerable endpoint. Additionally, attackers might be identified by monitoring for unusual delays or suspicious queries involving the 'userid' parameter. [2]
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 'userid' parameter, minimizing database user privileges by avoiding high-privilege accounts for routine operations, and conducting regular security audits of code and systems to detect and remediate vulnerabilities promptly. [2]