CVE-2025-62687VulnerabilityPublished 21 Nov 2025

CVE-2025-62687: LogStare Collector (for Windows) · Cross-site Request Forgery (CSRF)

Affects LogStare Collector (for Windows)Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.0 base score

6.5Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% 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:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: High
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: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 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
LogStare Inc. LogStare Collector (for Windows)	Affected <=2.4.1	Fixed in–

AI-suggested

1. Apply patches or updates from LogStare Inc. as soon as they become available to address the CSRF vulnerability directly. 2. Until patches are released, restrict access to the LogStare Collector management interface to trusted networks and users only, using network segmentation, VPNs, or firewall rules. 3. Implement web application firewall (WAF) rules to detect and block suspicious CSRF attack patterns targeting the LogStare Collector interface. 4. Educate and train administrators and users to avoid clicking on suspicious links or visiting untrusted websites while logged into the LogStare Collector interface. 5. Monitor logs and system behavior for unusual configuration changes or access patterns that could indicate exploitation attempts. 6. If possible, enable multi-factor authentication (MFA) on the management interface to reduce the risk of session hijacking or unauthorized access. 7. Review and harden session management and CSRF token implementation in the LogStare Collector configuration if customization is supported. 8. Conduct regular security assessments and penetration testing focused on the management interface to identify and remediate similar vulnerabilities proactively.

Description

Cross-site request forgery vulnerability exists in LogStare Collector. If a user views a crafted page while logged, unintended operations may be performed.

Impact

For European organizations, the impact of CVE-2025-62687 can be significant, especially for those relying on LogStare Collector for critical log management and security monitoring. Unauthorized changes to the log collection configuration could lead to loss of log integrity, disabling of important monitoring functions, or redirection of logs to attacker-controlled systems, undermining incident detection and response capabilities. This can increase the risk of undetected breaches or compliance violations under regulations such as GDPR, which mandate secure and reliable logging. Since the vulnerability requires user interaction, social engineering or phishing campaigns targeting administrators or operators of LogStare Collector could facilitate exploitation. The integrity compromise could also affect forensic investigations and audit trails, critical for regulatory compliance and cybersecurity operations. The absence of confidentiality or availability impact reduces the risk of data leakage or service downtime but does not diminish the importance of maintaining log integrity in security operations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats