CVE-2025-8437VulnerabilityPublished 1 Aug 2025

CVE-2025-8437: code-projects Kitchen Treasure · SQL Injection

Affects code-projects Kitchen TreasureSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 1 Aug 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 Kitchen Treasure	Affected =1.0	Fixed in–

AI-suggested

Given the absence of official patches, European organizations should immediately implement the following mitigations: 1) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the 'email' parameter in /userregistration.php. 2) Conduct thorough input validation and sanitization on all user-supplied data, especially the email field, using parameterized queries or prepared statements if source code access is available. 3) Restrict database user permissions to the minimum necessary to limit the impact of any injection attack. 4) Monitor application logs and database queries for unusual activity indicative of injection attempts. 5) If feasible, isolate the affected application environment from critical internal networks to contain potential breaches. 6) Engage with the vendor or community to track any forthcoming patches or updates and plan for timely application. 7) Consider temporary disabling or restricting access to the vulnerable registration functionality until a permanent fix is available.

Description

A vulnerability classified as critical has been found in code-projects Kitchen Treasure 1.0. This affects an unknown part of the file /userregistration.php. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using Kitchen Treasure 1.0, this vulnerability poses a significant risk to the confidentiality and integrity of user data, especially personal information collected during user registration. Exploitation could lead to unauthorized access to sensitive customer data, regulatory non-compliance (e.g., GDPR violations), and reputational damage. Additionally, attackers could manipulate or delete registration data, disrupting business operations and customer trust. Since the vulnerability can be exploited remotely without authentication, attackers from anywhere could target European deployments, increasing the threat landscape. The lack of vendor patches means organizations must rely on internal mitigations, which may not fully eliminate risk. This is particularly critical for sectors handling sensitive personal or financial data, such as hospitality, retail, or food service businesses using Kitchen Treasure for customer engagement or loyalty programs.

Summary

CVE-2025-8437 is a SQL Injection vulnerability identified in version 1.0 of the code-projects Kitchen Treasure application, specifically within the /userregistration.php file. The vulnerability arises from improper sanitization or validation of the 'email' parameter, which allows an attacker to inject malicious SQL code remotely without any authentication or user interaction. This injection can manipulate backend database queries, potentially leading to unauthorized data access, data modification, or even full compromise of the database. The CVSS 4.0 score of 6.9 categorizes it as a medium severity vulnerability, reflecting the ease of remote exploitation (no privileges or user interaction required) but with limited impact on confidentiality, integrity, and availability (all rated low). Although no known exploits are currently reported in the wild, the public disclosure of the vulnerability increases the risk of exploitation attempts. The absence of available patches or mitigations from the vendor further elevates the urgency for affected organizations to implement compensating controls. Given the nature of SQL Injection, attackers could extract sensitive user data, alter registration records, or disrupt service functionality, impacting both the integrity and availability of the application.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Aug 2025, 06:32 UTC

Technical details

References

Community reviews

Related threats