CVE-2026-65983
Awaiting Analysis Awaiting Analysis - Queue

Unauthenticated File Access in OpenEMR Prior to 8.2.0

Vulnerability report for CVE-2026-65983, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-05

Last updated on: 2026-11-05

Assigner: GitHub, Inc.

Description

OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.2.0, interface/modules/custom_modules/oe-module-faxsms/src/Controller/SignalWireClient.php decrypts a selected patient document with Document::get_data() and SignalWireClient::uploadFileForFax() writes the plaintext bytes under sites/{siteId}/fax. The module returns the resulting public URL to SignalWire, protects it only with a predictable uniqid() filename, and never removes the staged file. An unauthenticated network actor who obtains or guesses the URL can retrieve persistent patient documents even when drive encryption is enabled. This issue is fixed in version 8.2.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-05
Last Modified
2026-11-05
Generated
2026-11-08
AI Q&A
2026-11-06
EPSS Evaluated
2026-11-06
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
openemr openemr < 8.2.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
CWE-552 The product makes files or directories accessible to unauthorized actors, even though they should not be.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in OpenEMR involves the insecure handling of decrypted patient documents when using the SignalWire fax feature. The module decrypts a selected patient document and writes the plaintext bytes to a publicly accessible directory (sites/{siteId}/fax/) without proper authentication or file removal. The filenames are predictable using uniqid(), allowing unauthenticated actors to guess URLs and access sensitive patient data even when drive encryption is enabled.

Detection Guidance

Check for unprotected decrypted patient documents in sites/{siteId}/fax/ directories. Look for files with predictable uniqid() filenames. Verify if .htaccess protects the documents directory but not the fax directory. Search for unauthorized access logs to these files.

Impact Analysis

An unauthenticated attacker could retrieve persistent patient documents by accessing or guessing the predictable URLs where decrypted files are stored. This exposes protected health information (PHI) to unauthorized parties, violating patient privacy and potentially leading to data breaches or compliance violations.

Compliance Impact

This vulnerability likely violates HIPAA due to unauthorized access to PHI and inadequate safeguards for protected health information. GDPR compliance may also be impacted as it involves unauthorized processing and potential exposure of personal data. The exposure of PHI without proper controls undermines requirements for data confidentiality and integrity.

Mitigation Strategies

Upgrade OpenEMR to version 8.2.0 or later to apply the security fixes. Ensure the fax staging directory is moved to a protected location and files are encrypted at rest. Implement token-based access for staged files and remove any existing decrypted files from the vulnerable directory.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-65983. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...