Project Subscriptions
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 25 Feb 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 25 Feb 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Open-emr
Open-emr openemr |
|
| CPEs | cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Open-emr
Open-emr openemr |
Wed, 25 Feb 2026 12:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openemr
Openemr openemr |
|
| Vendors & Products |
Openemr
Openemr openemr |
Wed, 25 Feb 2026 02:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | OpenEMR has Broken Access Control in Report/Clients/Message List CSV Export | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-02-25T20:50:25.100Z
Reserved: 2026-01-29T14:03:42.539Z
Link: CVE-2026-25124
Updated: 2026-02-25T20:49:53.008Z
Status : Analyzed
Published: 2026-02-25T02:16:22.550
Modified: 2026-02-25T16:54:00.173
Link: CVE-2026-25124
No data.
OpenCVE Enrichment
Updated: 2026-02-25T11:35:11Z