CVE-2025-61949VulnerabilityPublished 21 Nov 2025

CVE-2025-61949: LogStare Collector (for Windows) · Cross-site scripting (XSS)

Affects LogStare Collector (for Windows)Source CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

5.4Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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 21 Nov 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-26.

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
LogStare Inc. LogStare Collector (for Windows)	Affected <=2.4.1	Fixed in–

AI-suggested

1. Apply official patches or updates from LogStare Inc. as soon as they are released to address this vulnerability. 2. In the absence of patches, implement strict input validation and output encoding on all user-supplied data within the UserManagement interface to prevent script injection. 3. Restrict access to the LogStare Collector management interface using network segmentation, VPNs, or IP whitelisting to limit exposure to trusted administrators only. 4. Enforce strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of unauthorized access. 5. Educate administrators about phishing and social engineering risks that could lead to exploitation of this vulnerability. 6. Monitor logs and management interface access for unusual activity or signs of attempted exploitation. 7. Consider deploying web application firewalls (WAF) with rules to detect and block XSS payloads targeting the management interface. 8. Regularly review and audit user accounts and permissions to minimize the number of users with management access.

Description

LogStare Collector contains a stored cross-site scripting vulnerability in UserManagement. If crafted user information is stored, an arbitrary script may be executed on the web browser of the user who logs in to the product's management page.

Impact

For European organizations, this vulnerability poses a risk to the confidentiality and integrity of log management systems. Successful exploitation could allow attackers to hijack sessions of administrators or users with management access, potentially leading to unauthorized changes in log configurations, deletion or tampering of logs, or exposure of sensitive operational data. This could undermine incident response capabilities and compliance with data protection regulations such as GDPR. Since LogStare Collector is used in sectors like critical infrastructure, finance, and government, exploitation could have downstream effects on operational security and regulatory compliance. The requirement for authentication and user interaction limits the attack surface but does not eliminate risk, especially in environments with multiple administrators or where phishing/social engineering could be used to lure victims. The absence of known exploits reduces immediate risk but should not lead to complacency. European organizations relying on LogStare Collector should consider this vulnerability a moderate threat that warrants timely remediation to maintain security and compliance.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Nov 2025, 07:49 UTC

Technical details

References

Community reviews

Related threats