CVE-2025-15012
BaseFortify
Publication date: 2025-12-22
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 |
|---|---|---|
| fabian | 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?
CVE-2025-15012 is a SQL injection vulnerability in version 1.0 of the Refugee Food Management System, specifically in the file /home/home.php. The vulnerability occurs because the application accepts user input via the parameter "a" without proper sanitization or validation, allowing attackers to inject malicious SQL code. This improper neutralization of special characters enables attackers to manipulate SQL queries remotely without authentication, potentially compromising the system's confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, alteration or deletion of database records, disruption of services, and full system compromise. Attackers can manipulate SQL queries to execute unauthorized database operations, potentially gaining full control over the system. Since exploitation requires no authentication and can be performed remotely, it poses a high risk to business continuity and system security. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying requests to the vulnerable file 'home.php' with the parameter 'a' being manipulated. One method is to use Google dorking with the query 'inurl:home/home.php' to find potentially vulnerable targets. Additionally, tools like sqlmap can be used to test for SQL injection by sending crafted POST requests to 'home.php' with the 'a' parameter. For example, using sqlmap: sqlmap -u "http://target/home/home.php" --data="a=1" --risk=3 --level=5 to enumerate databases and detect injection points. [1, 2]
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 mitigations currently exist. Additionally, implement prepared statements with parameter binding to separate SQL code from user input, enforce strict input validation and filtering on the 'a' parameter, and restrict database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. [1, 2]
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, since the vulnerability allows unauthorized access and manipulation of sensitive data, it could potentially lead to violations of data protection requirements under such regulations by compromising confidentiality, integrity, and availability of personal or sensitive information. Immediate remediation is critical to maintain data security and compliance. [1, 2, 3]