CVE-2025-15182
Remote SQL Injection in Refugee Food Management System
Publication date: 2025-12-29
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 |
|---|---|---|
| code-projects | refugee_food_management_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 a SQL injection weakness in the Refugee Food Management System 1.0, specifically in the /home/served.php file. By manipulating the argument 'refNo', an attacker can execute unauthorized SQL commands remotely, potentially compromising the database.
How can this vulnerability impact me? :
The vulnerability can allow remote attackers to execute arbitrary SQL commands, which may lead to unauthorized access, data leakage, data modification, or disruption of the system's normal operation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized remote attackers to perform SQL injection attacks, potentially leading to unauthorized access, data leakage, data tampering, and full system control. Such impacts on confidentiality, integrity, and availability of data can result in non-compliance with data protection standards and regulations like GDPR and HIPAA, which require safeguarding sensitive data against unauthorized access and ensuring data integrity. Therefore, this vulnerability poses a significant risk to compliance with these common standards and regulations. [1, 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 'refNo' parameter in the /home/served.php file for SQL injection. One approach is to use automated tools like sqlmap to test the endpoint. For example, you can run: sqlmap -u "http://target/home/served.php" --data="refNo=1" --risk=3 --level=5 to test for injection. Additionally, Google dorking with the query "inurl:home/served.php" can help identify vulnerable targets. Manual testing can involve sending crafted POST requests to served.php with manipulated refNo values to observe SQL errors or unexpected behavior. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate steps to mitigate this vulnerability include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Enforce strict input validation and filtering to ensure inputs conform to expected formats. 3) Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. Since no known countermeasures or patches are currently available, it is also suggested to replace the affected software with an alternative product to prevent exploitation. [1, 3]