# CVE-2023-6080: Privilege Escalation to SYSTEM in Lakeside Software Installer

> Local attackers can escalate privileges to SYSTEM level via the SysTrack LsiAgent Installer on Windows.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2024
- **Updated:** 1 Apr 2026
- **Also known as:** GHSA-75pc-2p8w-2hhf

## What is CVE-2023-6080?

CVE-2023-6080 is a high-severity vulnerability in Lakeside Software SysTrack LsiAgent Installer, published on 18 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Lakeside Software’s SysTrack LsiAgent Installer version 10.7.8 for Windows contains a local privilege escalation vulnerability which allows attackers SYSTEM level access.

Weakness: CWE-379 (Creation of Temporary File in Directory with Insecure Permissions)

## Which versions are affected by CVE-2023-6080?

It affects 1 product.


Products: Lakesidesoftware Systrack Lsiagent.

## How do I fix CVE-2023-6080?

No fix has been published for CVE-2023-6080 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-6080 being exploited?

There is no known exploitation of CVE-2023-6080 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6080 and fix it if it is affected.

What it is: CVE-2023-6080 is a high-severity vulnerability in Lakeside Software SysTrack LsiAgent Installer, published on 18 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6080 in the wild and no public exploit code.

Affected product: Lakeside Software SysTrack LsiAgent Installer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-6080/ (Markdown: https://insights.sbomify.com/CVE-2023-6080/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-6080
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-6080
- OSV: https://osv.dev/vulnerability/CVE-2023-6080

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-6080/
Summaries are generated and may contain mistakes; the official description above is the record.