CVE-2025-15186
SQL Injection in Refugee Food Management System /addusers.php
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 issue found in the Refugee Food Management System 1.0, specifically in the /home/addusers.php file. By manipulating the argument 'a', an attacker can inject malicious SQL code. The attack can be launched remotely and the exploit has been publicly disclosed.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to execute unauthorized SQL commands on the system's database remotely. This can lead to unauthorized data access, data modification, or data deletion, potentially compromising the integrity, confidentiality, and availability of the system's data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain information regarding the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the vulnerable parameter 'a' in the /home/addusers.php file for SQL injection flaws. One can use tools like sqlmap to automate detection, for example: sqlmap -u "http://target/home/addusers.php" --data="a=234" --risk=3 --level=5. Additionally, searching for the vulnerable URL using Google dorking with the query "inurl:home/addusers.php" can help identify exposed targets. Manual testing can involve sending crafted POST requests with SQL injection payloads to the 'a' parameter and observing the responses for SQL errors or unexpected behavior. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the vulnerable component or upgrading to a fixed version if available; 2) Implementing prepared statements with parameter binding to ensure user inputs are not directly incorporated into SQL queries; 3) Validating and filtering all user inputs rigorously to ensure they conform to expected formats; 4) Restricting database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations; 5) If immediate patching is not possible, consider disabling or restricting access to the vulnerable /home/addusers.php endpoint to prevent exploitation. [2, 3, 4]