CVE-2025-15212
SQL Injection in Refugee Food Management System Remote Exploitable
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-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 exists in the Refugee Food Management System 1.0, specifically in the processing of the file /home/regfood.php. By manipulating the argument 'a', an attacker can perform SQL injection, which allows remote exploitation of the system.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to remotely execute SQL injection attacks, potentially leading to unauthorized access, data leakage, data modification, or disruption of the system's normal operations.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable file /home/regfood.php and testing the parameter 'a' for SQL injection. One method is to use Google dorking with the query "inurl:home/regfood.php" to identify potentially vulnerable targets. For direct testing, you can use tools like sqlmap to test the parameter 'a' for SQL injection, for example: sqlmap -u "http://target/home/regfood.php?a=1" --batch. Additionally, manual testing by injecting SQL payloads into the 'a' parameter and observing the response can help detect the vulnerability. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate steps to mitigate this vulnerability include replacing the affected component with an alternative product, as no known countermeasures or mitigations have been documented. Additionally, avoid exposing the vulnerable endpoint publicly, apply input validation and sanitization on the 'a' parameter to prevent SQL injection, and monitor for any suspicious activity. Since the exploit is publicly available, urgent remediation is necessary to protect system security and data integrity. [3, 4]