VulnerabilityPublished 27 Jul 2025Updated 3 Nov 2025

CVE-2025-6241: Lakeside Software SysTrack · Uncontrolled Search Path Element

Affects Lakeside Software SysTrackSource CVE Database V5

Not known to be exploited · CVSS 4.4 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

4.4Medium

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: 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: 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 27 Jul 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 or the CVSS exploit maturity 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
Lakeside Software SysTrack	Affected =10.05.0027	Fixed in–

AI-suggested

Immediately audit and restrict write permissions on all directories included in the SYSTEM PATH environment variable to ensure they are not writable by non-privileged users.
Remove any user-writable directories from the SYSTEM PATH variable to prevent DLL hijacking.
Monitor and alert on changes to environment variables, especially SYSTEM PATH, to detect unauthorized modifications.
Implement application whitelisting to prevent unauthorized DLLs from loading.
Restrict local user permissions to prevent unauthorized service restarts or modifications to SysTrack components.
Once available, promptly apply official patches or updates from Lakeside Software addressing this vulnerability.
Conduct endpoint scans to detect presence of unauthorized DLLs in PATH directories.
Educate system administrators and users about the risks of modifying environment variables and the importance of secure configurations.
Employ endpoint detection and response (EDR) tools to monitor for suspicious DLL loading and privilege escalation attempts.
Consider isolating SysTrack agents on hardened systems with minimal user access to reduce attack vectors.

Description

LsiAgent.exe, a component of SysTrack from Lakeside Software, attempts to load several DLL files which are not present in the default installation. If a user-writable directory is present in the SYSTEM PATH environment variable, the user can write a malicious DLL to that directory with arbitrary code. This malicious DLL is executed in the context of NT AUTHORITY\SYSTEM upon service start or restart, due to the Windows default dynamic-link library search order, resulting in local elevation of privileges.

Impact

For European organizations, this vulnerability poses a risk of local privilege escalation, allowing attackers with local access to gain SYSTEM-level control over affected endpoints running SysTrack 10.05.0027. This can lead to unauthorized access to sensitive data, modification of system configurations, and potential lateral movement within corporate networks. Organizations relying on SysTrack for endpoint monitoring and analytics could see their monitoring infrastructure compromised, undermining security visibility and response capabilities. Although exploitation requires local access and user interaction, insider threats or attackers who have gained initial footholds could leverage this vulnerability to escalate privileges and deepen their control. The impact is particularly significant in environments with lax controls on PATH environment variables or where user-writable directories are inadvertently included in SYSTEM PATH. This could also affect managed service providers and enterprises with large deployments of SysTrack, increasing the attack surface. The absence of known exploits in the wild provides a window for proactive mitigation before active exploitation occurs.

CWE-427Uncontrolled Search Path Element (opens in a new tab)
Base weaknessOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.
Architecture and Design · Implementation · Attack Surface Reduction
Hard-code the search path to a set of known-safe values (such as system directories), or only allow them to be specified by the administrator in a configuration file. Do not allow these settings to be modified by an external party. Be careful to avoid related weaknesses such as CWE-426 and CWE-428.
Implementation · Attack Surface Reduction
When invoking other programs, specify those programs using fully-qualified pathnames. While this is an effective approach, code that uses fully-qualified pathnames might not be portable to other systems that do not use the same pathnames.
Implementation · Attack Surface Reduction
Remove or restrict all environment settings before invoking other programs. This includes the PATH environment variable, LD_LIBRARY_PATH, and other settings that identify the location of code libraries, and any application-specific search paths.
OWASP Cheat Sheets
Software Supply Chain Security (opens in a new tab)
Infrastructure as Code (opens in a new tab)
Attack patterns
Leveraging/Manipulating Configuration File Search Paths (opens in a new tab)
Search Order Hijacking (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 01:44 UTC

WeaknessesCWE-427

Technical details

References

Community reviews

Related threats