CVE-2025-11604
BaseFortify
Publication date: 2025-10-11
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 |
|---|---|---|
| projectworlds | online_food_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?
This vulnerability is an SQL injection in the Online Food Ordering System Project in PHP version 1.0, specifically in the file all-orders.php. It occurs because the 'status' parameter is directly concatenated into an SQL query without validation or sanitization, allowing attackers to inject malicious SQL code remotely without any authentication. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow unauthorized attackers to access, modify, or delete database records, upload malicious programs, and potentially destroy the server. Since no login is required, attackers can remotely perform these actions, leading to data breaches, data loss, and system compromise. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can lead to unauthorized access and manipulation of sensitive data, which may result in violations of data protection regulations such as GDPR and HIPAA. Failure to protect personal or health information due to such vulnerabilities can cause non-compliance, legal penalties, and loss of trust. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'status' parameter in the /all-orders.php endpoint for SQL injection. You can use SQL injection payloads such as: status=-1353' OR 7344=7344# to check if the application is vulnerable. For example, using curl: curl 'http://targetsite/all-orders.php?status=-1353'%20OR%207344=7344#' and observing if the response behavior changes or reveals database errors. Automated tools like sqlmap can also be used to test this parameter for SQL injection. [1]
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 'status' parameter to ensure it conforms to expected formats. 3) Minimize database user permissions to limit the impact of any exploitation. Additionally, monitor and restrict access to the vulnerable endpoint until a patch is applied. [1]