CVE-2025-58097VulnerabilityPublished 21 Nov 2025

CVE-2025-58097: LogStare Collector (for Windows) · Incorrect default permissions

Affects LogStare Collector (for Windows)Source CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

5.5Medium

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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: 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 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. Immediately review and restrict permissions on the LogStare Collector installation directory to ensure only administrators have write access. Use Windows ACL tools (e.g., icacls) to enforce strict permissions. 2. Monitor the installation directory for unauthorized file modifications using file integrity monitoring solutions. 3. Apply vendor patches or updates as soon as they become available to address the default permission misconfiguration. 4. Limit local user accounts with access to systems running LogStare Collector, enforcing the principle of least privilege. 5. Employ endpoint detection and response (EDR) tools to detect suspicious activities indicative of privilege escalation attempts. 6. Conduct regular audits of installed software permissions and configurations, especially for security-related tools running with elevated privileges. 7. Educate system administrators and security teams about this vulnerability to ensure timely response and remediation. 8. Consider isolating systems running LogStare Collector to reduce the risk of lateral movement if compromised.

Description

The installation directory of LogStare Collector is configured with incorrect access permissions. A non-administrative user may manipulate files within the installation directory and execute arbitrary code with the administrative privilege.

Impact

For European organizations, this vulnerability poses a risk of local privilege escalation on Windows systems running LogStare Collector. Successful exploitation could allow attackers or malicious insiders to execute arbitrary code with administrative privileges, potentially leading to full system compromise. This could undermine the integrity of log data collection and monitoring, critical for security operations and compliance. The impact is particularly concerning for sectors with stringent regulatory requirements such as finance, healthcare, and critical infrastructure, where log integrity is essential for forensic investigations and audit trails. Additionally, compromised administrative privileges could facilitate lateral movement within networks, increasing the risk of broader organizational impact. Although exploitation requires local access, the widespread use of Windows endpoints and the presence of internal threat actors or malware that gains initial foothold elevate the risk. The absence of known exploits in the wild reduces immediate urgency but does not eliminate the threat, especially as attackers often reverse-engineer disclosed vulnerabilities to develop exploits.

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