# CVE-2019-25257: LogicalDOC Enterprise 7.7.4 Authenticated Command Execution via Binary Path Manipulation

> Authenticated attackers can execute arbitrary OS commands by manipulating system binary paths in LogicalDOC Enterprise settings.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2025
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-xx8r-jj29-vw5j

## What is CVE-2019-25257?

CVE-2019-25257 is a high-severity command injection vulnerability in LogicalDOC Enterprise, published on 24 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LogicalDOC Enterprise 7.7.4 contains multiple authenticated OS command execution vulnerabilities that allow attackers to manipulate binary paths when changing system settings. Attackers can exploit these vulnerabilities by modifying configuration parameters like antivirus.command, ocr.Tesseract.path, and other system paths to execute arbitrary system commands with elevated privileges.

Weakness: CWE-426 (Untrusted Search Path)

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


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

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

## Is CVE-2019-25257 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25257 is a high-severity command injection vulnerability in LogicalDOC Enterprise, published on 24 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25257 exists.

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

## Sources

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

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