CVE-2025-15210
SQL Injection in Refugee Food Management System Allows Remote Exploit
Publication date: 2025-12-30
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 in the Refugee Food Management System 1.0, specifically in the file /home/editrefugee.php. It occurs due to manipulation of the argument a/b/c/sex/d/e/nationality_nid, allowing an attacker to inject malicious SQL code. The attack can be launched remotely and the exploit has been publicly disclosed.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute unauthorized SQL commands on the database, potentially leading to data leakage, data modification, or deletion. It may compromise the confidentiality, integrity, 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 searching for the presence of the vulnerable file `/home/editrefugee.php` and testing the input parameters `a/b/c/sex/d/e/nationality_nid` for SQL injection. One detection method is to use Google dorking with the query `inurl:home/editrefugee.php` to identify potentially vulnerable targets. For active testing on your system, you can use tools like sqlmap to test the URL with crafted payloads targeting these parameters. Example command: `sqlmap -u "http://target/home/editrefugee.php?a=1&b=2&c=3&sex=male&d=4&e=5&nationality_nid=6" --batch` to check for SQL injection vulnerabilities. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product, as no known countermeasures or patches have been documented. Additionally, restricting access to the vulnerable endpoint `/home/editrefugee.php` via network controls or web application firewalls may reduce exposure. Monitoring for exploit attempts and applying input validation or parameterized queries in the source code (if possible) are recommended longer-term fixes. [1]