● Medium · CVSS 6.5

How to Fix CVE-2026-32120: Critical Vulnerability in openemr

Q: Is CVE-2026-32120 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-32120?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for openemr run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-25086: Critical Vulnerability in WebCTRL Premium Server — Critical Vulnerability in WebCTRL Premium Server
How to Fix CVE-2026-39866: Command injection in lawnchair — Command injection in lawnchair
How to Fix CVE-2026-40259: Improper authorization in siyuan , Improper authorization in siyuan
How to Fix CVE-2026-2524: Critical Vulnerability in Open5GS , Critical Vulnerability in Open5GS
How to Fix CVE-2026-0862: Critical Vulnerability in Save as PDF Plugin by PDFCrowd , Critical Vulnerability in Save as PDF Plugin by PDFCrowd

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 6.5 - Medium
Actively exploited?	Not currently listed in CISA KEV
Affected	< 8.0.0.3
Fixed in	See vendor advisory
Type (CWE)	CWE-639: Authorization Bypass Through User-Controlled Key

What is CVE-2026-32120?

CVE-2026-32120 is a security flaw in openemr. OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0.3, an Insecure Direct Object Reference (IDOR) vulnerability in the fee sheet product save logic (library/FeeSheet.class.php) allows any authenticated user with fee sheet ACL access to delete, modify, or read drug_sales records belonging to arbitrary patients by manipulating the hidden prod[][sale_id] form field.

Why this CVE matters

Unpatched network-facing software is the leading initial-access vector in public breach reporting. Treat any CVSS-9 class flaw on an internet-reachable system as urgent, regardless of whether public exploit code has been observed yet.

For deployments of openemr that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

openemr: < 8.0.0.3

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open openemr's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-32120

Read the vendor advisory in full: https://github.com/openemr/openemr/security/advisories/GHSA-pvvj-mv7h-7847
Upgrade openemr to the patched build listed in the vendor advisory.
Back up the configuration (and database, where applicable) before upgrading.
Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
Restart the affected service so the patched binary loads, then verify the new version (see verification section).

The commands below are runnable starting points. Adapt the package name, target version, and host paths to your environment using the vendor advisory linked under References.

npm / Yarn / pnpm


# Vendor advisory: https://github.com/openemr/openemr/security/advisories/GHSA-pvvj-mv7h-7847
# Update to the patched release named in the advisory
npm install openemr@latest
# or pin to the exact fixed version from the vendor advisory
npm install openemr@<patched-version>
npm ls openemr

PyPI (pip / Poetry)


# Vendor advisory: https://github.com/openemr/openemr/security/advisories/GHSA-pvvj-mv7h-7847
pip install --upgrade openemr
pip show openemr | grep -i version
# Poetry:
poetry add openemr@^<patched-version>

Docker / container


# Vendor advisory: https://github.com/openemr/openemr/security/advisories/GHSA-pvvj-mv7h-7847
docker pull <your-registry>/openemr:<patched-tag>
docker stop <app> && docker rm <app>
docker run -d --name <app> <your-registry>/openemr:<patched-tag>

PowerShell detect/upgrade/verify/log (Windows)


# CVE-2026-32120 remediation runner. Adapt version checks to your environment.
$log = "C:\Logs\CVE-2026-32120-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }

try {
    Write-Log "Detect: checking installed product"
    $installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
        Where-Object { $_.Name -match 'openemr' }
    if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
    Write-Log "Found version $($installed.Version)"

    Write-Log "Backup: copying program files and registry hive"
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\CVE-2026-32120-$stamp"
    New-Item -ItemType Directory -Force -Path $backup | Out-Null
    Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
    reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null

    Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
    Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue

    Write-Log "Verify: re-reading product version"
    $after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'openemr' }
    Write-Log "Post-patch version: $($after.Version)"
    if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged; check vendor advisory" }
} catch {
    Write-Log "ERROR: $_"
    throw
}

Bash detect/upgrade/verify/log (Linux)


#!/usr/bin/env bash
# CVE-2026-32120 remediation runner. Re-runnable, exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-32120-fix.log; }

log "Detect: current openemr version"
if command -v dpkg >/dev/null 2>&1; then
    current=$(dpkg-query -W -f='${Version}' openemr 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' openemr 2>/dev/null || echo "not-installed")
else
    current="unknown"
fi
log "Current: $current"

log "Backup: snapshotting config"
backup="/var/backups/cve-2026-32120-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d /etc/openemr ] && cp -a /etc/openemr "$backup/" || true

log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq
    sudo apt-get install -y --only-upgrade openemr
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y openemr
elif command -v yum >/dev/null 2>&1; then
    sudo yum update -y openemr
fi

log "Verify: re-reading openemr version"
if command -v dpkg >/dev/null 2>&1; then
    after=$(dpkg-query -W -f='${Version}' openemr)
else
    after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' openemr)
fi
log "After: $after"

if [ "$after" != "$current" ]; then
    log "SUCCESS: openemr upgraded"
else
    log "WARN: version unchanged. Confirm the patched build is in your repository."
    exit 1
fi

If you cannot patch immediately

No official workaround exists beyond restricting network exposure to the affected component. Apply the vendor patch as the primary remediation.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-32120.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for log entries that do not match your normal request patterns, especially repeated requests to the same uncommon endpoint, and any administrative changes you cannot tie back to a known operator.

Frequently asked questions

Is CVE-2026-32120 being exploited in the wild?