Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-32120: OpenEMR has IDOR in Fee Sheet Product Save

MediumCVSS 6.3 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 25/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • No fixed version is recorded, but the references include a patch (commit or PR) link.

Low priority for now. See the fix and affected versions sections below.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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. The `save()` method uses the user-supplied `sale_id` in five SQL queries (SELECT, UPDATE, DELETE) without verifying that the record belongs to the current patient and encounter. Version 8.0.0.3 contains a patch.

Published
Mar 25, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 19th percentile

Report tools

JSON

Action score

25

Monitor

Low priority for now.

CVSS
25 / 40 · 6.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.3
CNA · GitHub_M
6.5
0.2 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-32120

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
open-emropenemr

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • openemr openemr

    • < 8.0.0.3affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • open-emr openemrbefore 8.0.0.3

Other highest-scoring records for the same primary product.

  • CVE-2018-17179An issue was discovered in OpenEMR before 5.0.1 Patch 7.
    60This week
  • CVE-2020-19364OpenEMR 5.0.1 allows an authenticated attacker to upload and execute malicious PHP scripts through /controller.php.
    56Plan
  • CVE-2019-14530An issue was discovered in custom/ajax_download.php in OpenEMR before 5.0.2 via the fileName parameter.
    55Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-33346Mar 19, 2026 · OpenEMR has stored XSS in portal_payment.php via Unescaped table_args
    34Monitor
  • ← EarlierCVE-2026-29187Mar 25, 2026 · OpenEMR Vulnerable to Authenticated Blind Boolean-Based SQL Injection in new_search_popup.php
    35Monitor
  • Later →CVE-2026-33348Mar 25, 2026 · OpenEMR has Stored XSS in patient encounter Eye Exam form $CHRONIC2 and $CHRONIC3
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-102940225 days apartOpenEMR: Missing Write ACL Allows Unauthorized Document Reassignment
    38Monitor
  • CVE-2026-2514726 days apartOpenEMR's Portal Payment Endpoint Trusts User-Controlled pid
    28Monitor
  • CVE-2026-2592728 days apartOpenEMR Missing Authorization Checks in DICOM Viewer State API
    28Monitor
  • CVE-2026-339310 days apartOpenEMR has IDOR in Portal Payment Page that Allows Cross-Patient Record Access
    26Monitor
  • CVE-2026-257446 days apartOpenEMR: POST /api/.../vital Accepts Attacker-Supplied id and Overwrites Arbitrary Vitals
    26Monitor
  • CVE-2026-333046 days apartOpenEMR has Authorization Bypass in Dated Reminders Log
    26Monitor

Not on record for this CVE: EPSS history · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

nvd-primary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const invoice = await Invoice.findById(req.params.id);res.json(invoice);

Fixed

ts
const invoice = await Invoice.findOne({  id: req.params.id,  ownerId: req.user.id,});if (!invoice) return res.sendStatus(404);res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records