dbcve.org
Logstare CollectorApplication · Secuavail

CVE-2025-58097

HIGH · 7.8 CVSS v3.1 Published 2025-11-21
Fix available
A fix is available. Upgrade to 2.4.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The LogStare Collector installation directory has overly permissive file system permissions (likely world-writable or group-writable). A non-privileged local user can replace executable files, scripts, or configuration files within the installation directory with malicious equivalents, causing the service running under an administrative account to execute arbitrary code upon service restart or related operations.

MitigationRestrict write permissions on the LogStare Collector installation directory to only administrative/system accounts, removing write access for standard users and unprivileged groups.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Logstare CollectorApplication
Affected:< 2.4.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate LogStare Collector installation
    Search common installation directories or check for running processes named 'LogStare Collector' or related services. On Windows, check C:\Program Files\Secuavail or C:\Program Files (x86)\Secuavail. On Linux, check /opt/secuavail or /usr/local/secuavail.
    Affected if LogStare Collector is found installed on the system
  2. Identify installed version
    Check the version of the installed LogStare Collector by examining the product version through the Windows registry, the executable's properties, or a version file within the installation directory.
    Affected if The installed version is less than 2.4.2 (any version from 1.x up to 2.4.1)
  3. Verify directory permissions
    Examine file system permissions on the LogStare Collector installation directory. On Windows, run 'icacls <installation_path>' from an elevated command prompt. On Linux, run 'ls -la <installation_path>' and check for world-writable (o+w) or group-writable (g+w) permissions.
    Affected if Standard non-privileged users or groups have write access to the installation directory
  4. Check executable file permissions
    Review permissions on executable files (.exe, .dll, .bat, .cmd, .sh) within the installation directory to see if they are writable by non-privileged accounts. Use 'icacls' on Windows or 'ls -la' on Linux.
    Affected if Executable files or scripts are writable by non-admin users

The system is affected if LogStare Collector version < 2.4.2 is installed and the installation directory or its executables are writable by non-privileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.2 or later
Fixed in 2.4.2
Interim mitigation

Restrict write permissions on the LogStare Collector installation directory to only administrative/system accounts, removing write access for standard users and unprivileged groups.

Recommended fix High confidence

2.4.2

  1. Back up the current LogStare Collector configuration and data directory
  2. Stop the LogStare Collector service
  3. Download LogStare Collector version 2.4.2 from the official vendor source (www.logstare.com)
  4. Install version 2.4.2 following standard installation procedures
  5. Verify the installation directory permissions are correctly set (restricted to administrative users only)
  6. Start the LogStare Collector service
  7. Confirm the service is running correctly and data collection is functioning

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Logstare Collector Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58097 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58097 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data