CVE-2025-8164: code-projects Public Chat Room · SQL Injection
Affects code-projects Public Chat RoomSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% 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:PExploitation evidence
Disclosed: evidence found.
CVE published 25 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubkbhjt/cvepkg:github/kbhjt/cveOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately audit their use of code-projects Public Chat Room to determine if version 1.0 is deployed. If so, they should consider the following specific actions: 1) Implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting the 'ID' parameter in send_message.php. 2) Apply input validation and parameterized queries or prepared statements in the application code to prevent injection if source code access and modification are possible. 3) Restrict database user permissions to the minimum necessary to limit the impact of any injection attack. 4) Monitor application logs and database activity for unusual queries or access patterns indicative of exploitation attempts. 5) If feasible, isolate or disable the vulnerable chat room service until a patch or updated version is available. 6) Engage with the vendor or community to obtain patches or updates addressing this vulnerability. 7) Educate IT and security teams about this specific vulnerability to enhance detection and response capabilities.
Description
A vulnerability has been found in code-projects Public Chat Room 1.0 and classified as critical. This vulnerability affects unknown code of the file send_message.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.