CVE-2025-7186VulnerabilityPublished 8 Jul 2025

CVE-2025-7186: code-projects Chat System · SQL Injection

Affects code-projects Chat 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.4% chance of exploitation in 30 days – higher than 40% 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 8 Jul 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
GitHublamentxu123/cve`pkg:github/lamentxu123/cve`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should first identify any deployments of code-projects Chat System version 1.0 within their environment. Since no official patches are currently available, immediate mitigation steps include implementing web application firewall (WAF) rules to detect and block SQL injection attempts targeting the /user/fetch_chat.php endpoint and the 'ID' parameter. Input validation and parameterized queries should be enforced if organizations have the capability to modify the source code. Network segmentation can limit exposure of the chat system to trusted users only. Monitoring logs for unusual database queries or repeated access attempts to the vulnerable endpoint can help detect exploitation attempts early. Organizations should also plan to upgrade or replace the chat system with a version that addresses this vulnerability once available. Additionally, conducting a thorough security review of all web-facing applications for similar injection flaws is recommended.

Description

A vulnerability was found in code-projects Chat System 1.0. It has been rated as critical. This issue affects some unknown processing of the file /user/fetch_chat.php. The manipulation of the argument ID leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using the code-projects Chat System 1.0, this vulnerability poses a risk of unauthorized data access or manipulation, potentially exposing sensitive communication data or user credentials. This could lead to privacy breaches under GDPR, reputational damage, and operational disruption if chat functionality is critical. The medium severity score suggests the impact is moderate but still significant, especially for organizations relying on this chat system for internal or customer communications. The lack of authentication requirement means attackers can exploit the vulnerability remotely, increasing the threat surface. However, since the affected product version is 1.0 and no known exploits are currently active, the immediate risk may be limited to organizations that have not updated or replaced this chat system. European organizations in sectors with strict data protection requirements (e.g., finance, healthcare, government) should be particularly cautious, as any data breach could lead to regulatory penalties.

Summary

CVE-2025-7186 is a SQL Injection vulnerability identified in version 1.0 of the code-projects Chat System, specifically affecting the /user/fetch_chat.php endpoint. The vulnerability arises from improper sanitization or validation of the 'ID' parameter, which is used in SQL queries. An attacker can manipulate this parameter to inject malicious SQL code, potentially allowing unauthorized access to or modification of the backend database. The vulnerability is remotely exploitable without requiring user interaction or authentication, increasing its risk profile. However, the CVSS 4.0 base score is 5.3 (medium severity), reflecting limited impact on confidentiality, integrity, and availability, with low complexity of attack but requiring low privileges. The vulnerability does not have known exploits in the wild yet, but public disclosure means attackers could develop exploits. The lack of patches or mitigation guidance from the vendor increases exposure. SQL Injection vulnerabilities can lead to data leakage, unauthorized data modification, or denial of service, depending on the database and application context. Given this is a chat system, sensitive user communications or credentials stored in the database could be at risk. The vulnerability's exploitation scope is limited to installations running version 1.0 of this specific chat system, which may not be widely deployed but could be present in niche or legacy environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Jul 2025, 22:04 UTC

Technical details

References

Community reviews

Related threats