OpenEMR has Authorization Bypass in Dated Reminders Log
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.0.0.2, an authorization bypass in the dated reminders log allows any authenticated non-admin user to view reminder messages belonging to other users, including associated patient names and free-text message content, by crafting a GET request with arbitrary user IDs in the `sentTo[]` or `sentBy[]` parameters. Version 8.0.0.2 fixes the issue.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-33304
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 13:50 UTC · Revision 1
Source evidence
OpenEMR has Authorization Bypass in Dated Reminders Log
core-osv · Original sourcePublished 19 Mar 2026, 20:27 UTC
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.0.0.2, an authorization bypass in the dated reminders log allows any authenticated non-admin user to view reminder messages belonging to other users, including associated patient names and free-text message content, by crafting a GET request with arbitrary user IDs in the `sentTo[]` or `sentBy[]` parameters. Version 8.0.0.2 fixes the issue.
osv:CVE-2026-33304
Complete source record
{
"id": "3b79bb0137f3a3c93bf8887b6aceb4946ea57143426dbefe895baac2a97ffd29",
"url": "https://osv.dev/vulnerability/CVE-2026-33304",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "OpenEMR has Authorization Bypass in Dated Reminders Log",
"summary": "OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.0.0.2, an authorization bypass in the dated reminders log allows any authenticated non-admin user to view reminder messages belonging to other users, including associated patient names and free-text message content, by crafting a GET request with arbitrary user IDs in the `sentTo[]` or `sentBy[]` parameters. Version 8.0.0.2 fixes the issue.",
"evidence": "osv:CVE-2026-33304",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-33304",
"aliases": [
"CVE-2026-33304",
"GHSA-66j9-ffq4-h222"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/openemr/openemr",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "d7ddb2dcb11332944c1e193ae0ac32eabe439f7c"
},
{
"fixed": "21dee7658a5f3b18c5750e3fae7324e875c1703a"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "8.0.0.2"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "21dee7658a5f3b18c5750e3fae7324e875c1703a"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v8_0_0_1",
"v8_0_0",
"v3_0_1",
"v3_0_0",
"v2_9_0",
"v2_8_3",
"v2_8_2",
"v2_8_1",
"v2_8_0",
"v2_7_3-rc1",
"v2_7_2",
"v2_7_2-rc2",
"v2_7_2-rc1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-33304.json"
}
}
],
"modified": "2026-10-28T02:30:35.860702205Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33304.json",
"https://github.com/openemr/openemr/security/advisories/GHSA-66j9-ffq4-h222",
"https://nvd.nist.gov/vuln/detail/CVE-2026-33304",
"https://github.com/openemr/openemr/commit/21dee7658a5f3b18c5750e3fae7324e875c1703a"
],
"provider_metadata": {
"cwe_ids": [
"CWE-639",
"CWE-862"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33304.json"
}
},
"related_cves": [
{
"value": "CVE-2026-33304",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 503240,
"published_at": "2026-03-19T20:27:00.84+00:00"
}