CVE-2025-15185
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection flaw found in the Refugee Food Management System 1.0, specifically in the file /home/refugeesreport.php. An attacker can manipulate the argument 'a' remotely to inject malicious SQL code, potentially compromising the database.
How can this vulnerability impact me? :
The SQL injection vulnerability can allow an attacker to access, modify, or delete sensitive data stored in the database. This can lead to data breaches, loss of data integrity, and unauthorized access to confidential information.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized database access, sensitive data leakage, data tampering, and full system compromise, which can lead to violations of data protection requirements under standards like GDPR and HIPAA. Exploitation threatens system security and business continuity, potentially resulting in non-compliance with regulations that mandate protection of personal and sensitive information. Immediate remediation is necessary to maintain data integrity and security. [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 'a' parameter in the /home/refugeesreport.php file for SQL injection. One common approach is to use automated tools like sqlmap to test and enumerate the database via this parameter. For example, a command such as `sqlmap -u "http://target/refugeesreport.php?a=1" --batch` can be used to detect and exploit the SQL injection. Additionally, searching for vulnerable targets using Google dorking with queries like `inurl:home/refugeesreport.php` can help identify affected systems. A proof-of-concept exploit involves sending crafted POST requests with malicious input in the 'a' parameter to confirm the vulnerability. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with an alternative product if possible, as no known mitigations exist for this version. 2) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 3) Applying strict input validation and filtering to ensure inputs conform to expected formats and block malicious data. 4) Minimizing database user permissions by avoiding elevated privilege accounts for routine operations. These corrective actions are critical to protect system integrity and data security. [1, 3, 2]