CVE-2025-15209VulnerabilityPublished 29 Dec 2025

CVE-2025-15209: code-projects Refugee Food Management System · SQL Injection

Affects code-projects Refugee Food Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects Refugee Food Management System	Affected =1.0	Fixed in–

AI-suggested

Immediate mitigation should focus on input validation and sanitization for all parameters (a, b, c, d) in /home/editfood.php. Developers must implement parameterized queries or prepared statements to prevent SQL injection. Until an official patch is released, organizations should conduct code audits to identify and fix unsafe SQL query constructions. Deploying Web Application Firewalls (WAFs) with rules targeting SQL injection patterns can provide temporary protection. Network segmentation and restricting access to the management system to trusted IPs can reduce exposure. Regular monitoring of logs for suspicious query patterns or anomalous database activity is essential. Organizations should also ensure backups of critical data are current to enable recovery in case of data tampering. Training staff on secure coding practices and incident response readiness will help mitigate future risks. Finally, engaging with the vendor or community for updates and patches is critical.

Description

A weakness has been identified in code-projects Refugee Food Management System 1.0. This affects an unknown part of the file /home/editfood.php. This manipulation of the argument a/b/c/d causes sql injection. The attack may be initiated remotely. The exploit has been made available to the public and could be exploited.

Impact

For European organizations, particularly NGOs, governmental agencies, and humanitarian groups managing refugee food distribution, this vulnerability poses a significant risk. Exploitation could lead to unauthorized access to sensitive personal data of refugees, manipulation of food supply records, or disruption of food management operations. Such impacts could undermine trust, violate data protection regulations like GDPR, and cause operational delays or shortages in critical aid delivery. The medium severity indicates moderate risk, but the public availability of exploits increases urgency. Organizations relying on this system may face reputational damage and legal consequences if data breaches occur. Additionally, disruption in food management could exacerbate humanitarian crises. The vulnerability's remote exploitability without authentication makes it accessible to a wide range of attackers, including opportunistic threat actors and potentially state-sponsored groups interested in destabilizing refugee support systems.

Summary

CVE-2025-15209 identifies a SQL injection vulnerability in the code-projects Refugee Food Management System version 1.0, specifically within the /home/editfood.php file. The vulnerability arises from improper validation or sanitization of input parameters labeled a, b, c, and d, which are susceptible to malicious SQL payloads. An attacker can remotely exploit this flaw without requiring authentication or user interaction, sending crafted requests that manipulate the SQL queries executed by the backend database. This can lead to unauthorized data disclosure, data modification, or potentially database corruption. The CVSS 4.0 base score is 5.3 (medium), reflecting network attack vector, low attack complexity, no privileges or user interaction needed, but limited impact on confidentiality, integrity, and availability. The exploit code has been publicly disclosed, increasing the risk of exploitation, although no active exploitation has been reported yet. The Refugee Food Management System is likely deployed in humanitarian contexts to manage food distribution for refugees, making the confidentiality and integrity of data critical. The vulnerability's presence in a core file handling food data editing suggests attackers could manipulate food supply records or extract sensitive beneficiary information. No official patches or updates have been linked yet, indicating that affected organizations must implement immediate mitigations or code reviews to prevent exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Dec 2025, 22:39 UTC

Technical details

References

Community reviews

Related threats