CVE-2025-62189VulnerabilityPublished 21 Nov 2025

CVE-2025-62189: LogStare Collector (for Windows) · Incorrect Authorization

Affects LogStare Collector (for Windows)Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.0 base score

4.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
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: None: The vulnerable system can be exploited without any interaction from any user.
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: 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 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

To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Restrict network access to the LogStare Collector UserRegistration endpoint by applying firewall rules or network segmentation to limit exposure to trusted administrative hosts only. 2) Monitor logs and audit trails for unusual user account creation activities or unexpected HTTP requests targeting the UserRegistration functionality. 3) Enforce strict internal access controls and least privilege principles to minimize the number of users with access to LogStare Collector interfaces. 4) Engage with LogStare Inc. to obtain patches or updates addressing this vulnerability as soon as they become available and prioritize timely deployment. 5) Consider deploying Web Application Firewalls (WAFs) or intrusion detection systems (IDS) with custom rules to detect and block crafted HTTP requests attempting unauthorized user creation. 6) Conduct internal security awareness and training to ensure administrators recognize signs of exploitation attempts. 7) Regularly review and harden configuration settings of LogStare Collector to disable or restrict unnecessary registration or user management features if possible.

Description

LogStare Collector contains an incorrect authorization vulnerability in UserRegistration. If exploited, a non-administrative user may create a new user account by sending a crafted HTTP request.

Impact

For European organizations, this vulnerability poses a risk of unauthorized user account creation within LogStare Collector deployments, potentially leading to privilege escalation and unauthorized access to log data or system controls. This could compromise the integrity of security monitoring and incident detection, undermining trust in log data and enabling attackers to hide their activities. Organizations in sectors relying heavily on log management for compliance and security, such as finance, energy, and critical infrastructure, may face increased risk. The medium severity score indicates moderate risk, but the potential for internal misuse or lateral movement elevates concern. If exploited, attackers could gain footholds within monitoring infrastructure, complicating incident response and increasing the likelihood of broader compromise. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially in environments with weak internal access controls or exposed management interfaces.

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