# CVE-2019-25307: WorkgroupMail 7.5.1 - 'WorkgroupMail' Unquoted Service Path

> Local attackers can execute arbitrary code with LocalSystem privileges by exploiting an unquoted service path in WorkgroupMail.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 11 Feb 2026
- **Updated:** 11 Feb 2026
- **Also known as:** GHSA-rx9j-2fmr-2gqf

## What is CVE-2019-25307?

CVE-2019-25307 is a high-severity vulnerability in Softalk WorkgroupMail, published on 11 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WorkgroupMail 7.5.1 contains an unquoted service path vulnerability in its Windows service configuration that allows local attackers to potentially execute arbitrary code. Attackers can exploit the unquoted binary path to inject malicious executables that will be run with LocalSystem privileges during service startup.

Weakness: CWE-428 (Unquoted Search Path or Element)

## Which versions are affected by CVE-2019-25307?


## How do I fix CVE-2019-25307?

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

## Is CVE-2019-25307 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25307 and fix it if it is affected.

What it is: CVE-2019-25307 is a high-severity vulnerability in Softalk WorkgroupMail, published on 11 Feb 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-2019-25307 exists.

Affected product: Softalk WorkgroupMail. 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-2019-25307/ (Markdown: https://insights.sbomify.com/CVE-2019-25307/index.md)
```

## Sources

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

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