CVE-2025-15185

7.3

code-projects · Refugee Food Management System

The Refugee Food Management System contains an unauthenticated SQL injection vulnerability in the refugeesreport.php file, allowing remote attackers to manipulate database queries via the 'a' parameter.

Executive summary

A critical SQL injection vulnerability in the Refugee Food Management System (version 1.0) allows unauthenticated remote attackers to compromise the underlying database.

Vulnerability

This is a classic SQL injection (CWE-89) vulnerability located in the refugeesreport.php file. An unauthenticated attacker can supply malicious input via the 'a' parameter, which is processed by the application without sufficient sanitization or validation.

Business impact

The vulnerability poses a severe risk to business operations and data security. Successful exploitation allows unauthorized parties to bypass access controls, extract sensitive information, modify or delete database records, and potentially gain full control over the application environment. Given the CVSS score of 7.3, this flaw represents a significant threat to confidentiality, integrity, and availability.

Remediation

Immediate Action: As no official patch is currently available, administrators should restrict network access to the application or take the service offline until the source code can be manually hardened.

Proactive Monitoring: Security teams should audit web server access logs for anomalous POST requests to refugeesreport.php, specifically searching for payloads containing SQL keywords or characters like single quotes and comment indicators.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SQL injection patterns in HTTP request parameters.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists as documented in the researcher's GitHub issue report.

Analyst recommendation

Given the availability of a public proof-of-concept and the ease of exploitation, this vulnerability should be treated with high urgency. Administrators must implement compensating controls immediately to prevent unauthorized database access and prioritize the development or application of a secure code fix to sanitize the 'a' parameter.

More code-projects CVEs

Sources

Originally found and disclosed by chenxiaodong (VulDB User), per the CVE Program record.