VulnerabilityPublished 15 Jan 2026

CVE-2025-67025: anycomment · Cross-site Scripting

Affects anycommentSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

6.1Medium

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

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

CVSS:3.1/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 15 Jan 2026
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 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
npmanycomment`pkg:npm/anycomment`Other threats	Affected =0.4.4	Fixed in–

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

AI-suggested

To mitigate CVE-2025-67025, European organizations should implement strict input validation and output encoding on all user-generated content within the Anycomment platform. Employing Content Security Policy (CSP) headers can help restrict the execution of unauthorized scripts. Organizations should consider disabling or restricting the comment feature temporarily if feasible until a patch is available. Web Application Firewalls (WAFs) can be configured to detect and block common XSS payloads targeting the comment section. Regular security audits and penetration testing focused on user input handling should be conducted. Monitoring logs for unusual activity related to comment submissions can provide early detection of exploitation attempts. Organizations should also engage with the Anycomment vendor or community to track patch releases and apply updates promptly. Educating web administrators and developers on secure coding practices for handling user input is essential for long-term prevention.

Description

CVE-2025-67025 is a Cross Site Scripting (XSS) vulnerability found in Anycomment version 0.4.4 that allows remote attackers to execute arbitrary code via the comment section. The vulnerability requires no privileges but does require user interaction, such as clicking a malicious link or viewing a crafted comment. It has a CVSS score of 6.1, indicating medium severity, with impacts primarily on confidentiality and integrity but not availability. There are no known exploits in the wild yet, and no patches have been published. European organizations using Anycomment for website comment functionality could be at risk of session hijacking, credential theft, or defacement. Mitigation involves input validation, output encoding, and restricting script execution in comments. Countries with higher adoption of Anycomment or significant web presence are more likely to be affected.

Impact

For European organizations, the impact of CVE-2025-67025 can be significant, especially for those relying on Anycomment to manage user interactions on their websites. Exploitation could lead to unauthorized disclosure of sensitive information, such as session tokens or personal data, compromising user privacy and potentially violating GDPR regulations. Integrity could be undermined by attackers injecting misleading or malicious content, damaging brand reputation and user trust. Although availability is not directly affected, the indirect consequences of successful attacks could include increased support costs and legal liabilities. Organizations in sectors with high web traffic, such as media, e-commerce, and public services, are particularly vulnerable. The absence of patches means organizations must rely on immediate mitigation strategies to reduce exposure. Additionally, the scope change in the CVSS vector suggests that the vulnerability could affect other integrated systems or services, increasing the potential attack surface.

Summary

CVE-2025-67025 is a Cross Site Scripting (XSS) vulnerability classified under CWE-79, affecting Anycomment version 0.4.4, a web-based commenting platform. The vulnerability allows a remote attacker to inject malicious scripts into the comment section, which are then executed in the context of other users' browsers when they view the compromised comments. This attack vector requires no authentication (PR:N) but does require user interaction (UI:R), such as clicking on or viewing a maliciously crafted comment. The vulnerability has a CVSS v3.1 base score of 6.1, reflecting medium severity, with an attack vector of network (AV:N), low attack complexity (AC:L), and a scope change (S:C) indicating that the vulnerability affects resources beyond the initially vulnerable component. The impact affects confidentiality and integrity (C:L/I:L) but not availability (A:N). The vulnerability could enable attackers to steal session cookies, perform actions on behalf of users, or redirect users to malicious sites. No patches or official fixes have been released as of the publication date, and no known exploits have been observed in the wild. The lack of patching increases the risk of exploitation if attackers develop proof-of-concept code. The vulnerability underscores the importance of sanitizing and encoding user input in web applications, especially those handling dynamic content such as comments.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Jan 2026, 21:33 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats