CVE-2025-15181
SQL Injection in Refugee Food Management System Allows Remote Exploitation
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this SQL injection vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, given that the vulnerability allows unauthorized database access, data leakage, and data tampering, it could potentially lead to non-compliance with data protection regulations that require safeguarding personal and sensitive data. Immediate remediation is critical to maintain data integrity and confidentiality, which are key aspects of such regulations. [2, 3, 4]
Can you explain this vulnerability to me?
This vulnerability is a SQL injection flaw in the Refugee Food Management System 1.0, specifically in an unknown function within the file /home/pagenateRefugeesList.php. By manipulating the 'rfid' argument, an attacker can inject malicious SQL code. This vulnerability can be exploited remotely and the exploit code has been made public.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to execute arbitrary SQL commands on the database, potentially leading to unauthorized access, data leakage, data modification, or deletion. This can compromise the integrity, confidentiality, and availability of the system's data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'rfid' parameter in the file '/home/pagenateRefugeesList.php' for SQL injection. A practical approach is to use automated tools like sqlmap to send crafted GET requests manipulating the 'rfid' parameter to check for SQL injection flaws. Additionally, attackers can be identified by monitoring for suspicious requests targeting 'pagenateRefugeesList.php' with unusual or malicious 'rfid' parameter values. Google dorking with queries such as 'inurl:home/pagenateRefugeesList.php' can help identify vulnerable instances exposed on the internet. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected component with an alternative product if possible, as no known countermeasures are documented; 2) Implementing prepared statements with parameter binding to separate SQL code from user input; 3) Applying strict input validation and filtering on the 'rfid' parameter to ensure it conforms to expected formats; 4) Restricting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations; and 5) Monitoring and blocking suspicious requests targeting the vulnerable endpoint. These measures help prevent exploitation and protect system security and data integrity. [2, 3]