VulnerabilityPublished 16 Oct 2025

CVE-2025-58115: NEOJAPAN ChatLuck · Cross-site Scripting (XSS)

Affects NEOJAPAN ChatLuckSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.0 base score

6.1Medium

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

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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 impacted component.
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 on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Oct 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 26 Oct 2026.

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 or the CVSS exploit maturity 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
NEOJAPAN Inc. ChatLuck	Affected >=3.6 <=6.6	Fixed in–

AI-suggested

To mitigate CVE-2025-58115, organizations should first verify if they use affected versions of ChatLuck (V3.6 R1.0 to V6.6 R1.0) and plan for immediate upgrades once patches are released by NEOJAPAN Inc. In the absence of official patches, implement strict input validation and sanitization on all user-supplied data in the Guest User Sign-up feature to prevent script injection. Deploy Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing ChatLuck. Enable HTTP-only and secure flags on cookies to reduce the risk of session hijacking. Conduct user awareness training focusing on recognizing suspicious links or inputs, especially for guest users who might be targeted. Monitor application logs for unusual input patterns or error messages indicative of attempted XSS exploitation. If possible, isolate the Guest User Sign-up functionality behind additional verification or CAPTCHA to reduce automated attacks. Engage with NEOJAPAN Inc. for timely updates and security advisories. Finally, consider deploying web application firewalls (WAF) with rules tailored to detect and block XSS payloads targeting ChatLuck.

Description

ChatLuck contains a cross-site scripting vulnerability in Guest User Sign-up. If exploited, an arbitrary script may be executed on the web browser of the user who is accessing the product.

Impact

For European organizations, the impact of this XSS vulnerability in ChatLuck can be significant, especially for those relying on this tool for internal and external communications. Successful exploitation could lead to unauthorized disclosure of sensitive information such as session tokens, user credentials, or confidential messages, undermining confidentiality. Integrity may be compromised by attackers injecting malicious scripts that alter displayed content or perform unauthorized actions on behalf of users. Although availability is not directly affected, the trustworthiness of the communication platform could be damaged, potentially disrupting collaboration workflows. Given that ChatLuck is a collaboration tool, attackers could use this vulnerability to conduct phishing campaigns within organizations or pivot to further attacks. The requirement for user interaction means social engineering could be employed to increase success rates. The absence of known exploits in the wild currently reduces immediate risk, but the public disclosure increases the likelihood of future exploitation attempts. Organizations in sectors with high collaboration needs, such as finance, government, and technology, are particularly at risk.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Oct 2025, 09:15 UTC

Technical details

References

Community reviews

Related threats