# CVE-2018-25359: Splinterware System Scheduler Pro 5.12 Privilege Escalation

> Low-privilege users can escalate privileges to LocalSystem by replacing the service executable due to insecure file permissions.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-crfv-m32j-v6c2

## What is CVE-2018-25359?

CVE-2018-25359 is a high-severity vulnerability in Splinterware System Scheduler Pro, published on 25 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Splinterware System Scheduler Pro 5.12 contains an insecure file permissions vulnerability that allows low-privilege users to escalate privileges by modifying service executable files. Attackers can rename the WService.exe file in the installation directory and replace it with a malicious executable that executes with LocalSystem privileges when the service is triggered.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2018-25359?


## How do I fix CVE-2018-25359?

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

## Is CVE-2018-25359 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25359 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25359 and fix it if it is affected.

What it is: CVE-2018-25359 is a high-severity vulnerability in Splinterware System Scheduler Pro, published on 25 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25359 exists.

Affected product: Splinterware System Scheduler Pro. 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-2018-25359/ (Markdown: https://insights.sbomify.com/CVE-2018-25359/index.md)
```

## Sources

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

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