CVE-2025-7951VulnerabilityPublished 22 Jul 2025

CVE-2025-7951: code-projects Public Chat Room · Cross Site Scripting

Affects code-projects Public Chat RoomSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% 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:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
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: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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 22 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
code-projects Public Chat Room	Affected =1.0	Fixed in–

AI-suggested

1. Immediate mitigation should include implementing strict input validation and output encoding on the chat_msg and your_name parameters to neutralize malicious scripts. 2. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the chat application context. 3. If possible, disable or restrict the use of the vulnerable chat room until a vendor patch or update is available. 4. Educate users about the risks of interacting with suspicious messages and encourage reporting of unusual chat activity. 5. Monitor web application logs for unusual input patterns that may indicate attempted exploitation. 6. Use web application firewalls (WAF) with rules specifically designed to detect and block XSS payloads targeting the chat application. 7. Conduct regular security assessments and penetration testing focused on the chat application to identify and remediate similar vulnerabilities proactively. 8. Engage with the vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available.

Description

A vulnerability classified as problematic has been found in code-projects Public Chat Room 1.0. This affects an unknown part of the file /send_message.php. The manipulation of the argument chat_msg/your_name leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations, the impact of this XSS vulnerability can be significant, especially for those relying on the code-projects Public Chat Room 1.0 for internal or customer-facing communications. Exploitation could lead to session hijacking, credential theft, or phishing attacks within the chat environment, undermining user trust and potentially exposing sensitive communication data. This could result in reputational damage, regulatory non-compliance (e.g., GDPR violations if personal data is compromised), and financial losses. Since the vulnerability requires user interaction, social engineering campaigns could be used to increase the likelihood of successful exploitation. Additionally, attackers could use the vulnerability as a foothold to escalate attacks within the network if the chat room is integrated with other internal systems. The medium severity rating suggests that while the threat is not critical, it should not be underestimated, particularly in sectors with high data sensitivity such as finance, healthcare, and government institutions in Europe.

Summary

CVE-2025-7951 is a cross-site scripting (XSS) vulnerability identified in version 1.0 of the code-projects Public Chat Room application. The vulnerability resides in the /send_message.php endpoint, specifically in the handling of the chat_msg and your_name parameters. An attacker can manipulate these input parameters to inject malicious scripts that execute in the context of other users' browsers when they view the chat messages. This vulnerability is remotely exploitable without authentication, requiring only user interaction to trigger the malicious payload. The vulnerability has been publicly disclosed, increasing the risk of exploitation, although no known active exploits have been reported in the wild to date. The CVSS v4.0 score is 5.1, indicating a medium severity level. The attack vector is network-based with low attack complexity, no privileges required, but user interaction is necessary to activate the malicious script. The impact primarily affects the confidentiality and integrity of user data by potentially stealing session cookies, redirecting users to malicious sites, or performing actions on behalf of the user within the chat application. Availability impact is minimal. Since the vulnerability affects a public-facing chat application, it can be leveraged to target multiple users simultaneously, especially in environments where the application is widely deployed. The lack of a patch or mitigation information in the provided data suggests that organizations using this software need to implement immediate protective measures to reduce risk.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Jul 2025, 03:01 UTC

Technical details

References

Community reviews

Related threats