# CVE-2026-39932: OpenEMR 8.2.0 Remote Code Execution via CategoryTree eval() Injection

> Authenticated administrators can achieve remote code execution by injecting PHP payloads into the category tree, which are executed via eval() on various pages.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-pj78-c8jq-8xhf

## What is CVE-2026-39932?

CVE-2026-39932 is a critical code injection vulnerability in Open-Emr Openemr, published on 3 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

OpenEMR through 8.2.0 contains a remote code execution vulnerability in the document category tree component (library/classes/Tree.class.php) that allows authenticated administrators to execute arbitrary operating system commands by injecting PHP payloads into the categories database table. Attackers can chain arbitrary SQL execution to alter the id column type to VARCHAR and insert a malicious PHP payload, which is then executed via an unsanitized eval() call whenever any page instantiates CategoryTree, including unauthenticated and low-privilege pages, resulting in command execution as the web server user.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

## Which versions are affected by CVE-2026-39932?

It affects 1 product.


Products: Open-Emr Openemr.

## How do I fix CVE-2026-39932?

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

## Is CVE-2026-39932 being exploited?

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

## Other vulnerabilities in Open-Emr Openemr

- [CVE-2026-24898](https://insights.sbomify.com/CVE-2026-24898/): OpenEMR has an Unauthenticated MedEx Token Disclosure (critical 10.0)
- [CVE-2026-24849](https://insights.sbomify.com/CVE-2026-24849/): OpenEMR Arbitrary File Read Vulnerability (critical 10.0)
- [CVE-2026-24908](https://insights.sbomify.com/CVE-2026-24908/): OpenEMR has SQL Injection in Patient API Sort Parameter (critical 10.0)
- [CVE-2022-2734](https://insights.sbomify.com/CVE-2022-2734/): Improper Restriction of Rendered UI Layers or Frames in openemr/openemr (critical 10.0)
- [CVE-2024-22611](https://insights.sbomify.com/CVE-2024-22611/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-39932 and fix it if it is affected.

What it is: CVE-2026-39932 is a critical code injection vulnerability in Open-Emr Openemr, published on 3 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39932 exists.

Affected product: Open-Emr Openemr. 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-2026-39932/ (Markdown: https://insights.sbomify.com/CVE-2026-39932/index.md)
```

## Sources

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

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