CVE-2026-25124 json
OpenEMR has Broken Access Control in Report/Clients/Message List CSV Export
published 2026-02-25 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-8583
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0, the OpenEMR application is vulnerable to an access control flaw that allows low-privileged users, such as receptionists, to export the entire message list containing sensitive patient and user data. The vulnerability lies in the message_list.php report export functionality, where there is no permission check before executing sensitive database queries. The only control in place is CSRF token verification, which does not prevent unauthorized data access if the token is acquired through other means. Version 8.0.0 fixes the vulnerability.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/openemr/openemr/security/advisories/GHSA-q7p5-rrwj-qmp2 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- openemr openemr
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
github.com
/openemr/openemr/commit/ad902d6892482fff2e3c56bfb15597df8b6c3beb
patch
-
github.com
/openemr/openemr/security/advisories/GHSA-q7p5-rrwj-qmp2
exploit, mitigation, vendor-advisory
Sources
- CVE List CVE-2026-25124
- NVD CVE-2026-25124
Fencer Vulns 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.