CVE-2026-65983 json
OpenEMR FaxSMS module: insecure staging of decrypted patient documents in webroot
published 3mo ago modified yesterday also EUVD-2026-117762 , GHSA-vv5j-6gjw-ffx9
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository openemr/openemr. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- open-emr openemr 8.2.0
- github.com/openemr/openemr@406bb70 commit
- github.com/openemr/openemr#12766 pull request
- github.com/openemr/openemr/releases/tag/v8_2_0 release
Is CVE-2026-65983 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2d ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/openemr/openemr/security/advisories/GHSA-vv5j-6gjw-ffx9 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- openemr openemr
Classification
References
-
github.com
/openemr/openemr/pull/12766
issue-tracking, patch
-
github.com
/openemr/openemr/commit/406bb7015e894c243936b0817d7c7060686a13d9
patch
-
github.com
/openemr/openemr/security/advisories/GHSA-vv5j-6gjw-ffx9
exploit, mitigation, vendor-advisory, advisory
-
github.com
/openemr/openemr/releases/tag/v8_2_0
product, release-notes
Sources
- CVE List CVE-2026-65983
- NVD CVE-2026-65983
- Maintainer advisory GHSA-vv5j-6gjw-ffx9
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of openemr/openemr published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.