CVE-2026-33305

OpenEMR has Authorization Bypass in FaxSMS AppDispatch Constructor

Published Mar 19, 2026 CVSS 3.1 · 5.4 Medium EPSS < 1% KEV · Not listed
Description
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 optional FaxSMS module (`oe-module-faxsms`) allows any authenticated OpenEMR user to invoke controller methods — including `getNotificationLog()`, which returns patient appointment data (PHI) — regardless of whether they hold the required ACL permissions. The `AppDispatch` constructor dispatches user-controlled actions and exits the process before any calling code can enforce ACL checks. Version 8.0.0.2 fixes the issue.

Analysis

AI-generated

Technical impact

OpenEMR's optional FaxSMS module contains an authorization bypass in the AppDispatch constructor. The constructor accepts actions supplied by an authenticated user and exits before any calling code can enforce ACL checks. Consequently, methods such as getNotificationLog() can be invoked by any authenticated user, exposing patient appointment data that is considered PHI. The flaw lies entirely in the lack of permission verification, allowing unauthorized disclosure of confidential health information.

Affected Systems

All installations of OpenEMR running versions prior to 8.0.0.2, including those that include the FaxSMS optional module, are affected. The issue is limited to the FaxSMS module and does not impact the core OpenEMR functionality. Versions 8.0.0.2 and later contain the necessary fix.

Risk and Exploitability

The vulnerability has a CVSS score of 5.4, classifying it as a medium severity issue. The EPSS score is below 1%, and the vulnerability is not listed in the CISA KEV catalog. Attack requires the attacker to be an authenticated user within the OpenEMR system; no remote code execution or privilege escalation is possible. Because the flaw allows the retrieval of PHI without proper authorization, the potential impact on confidentiality is significant for affected users.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest OpenEMR patch (8.0.0.2 or later).
  • If upgrading is not immediately possible, disable the FaxSMS module or restrict its use through ACLs.
  • Verify that getNotificationLog is no longer callable by users without permission.
  • Monitor application logs for suspicious notification log calls.

Generated by OpenCVE AI on March 20, 2026 at 16:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

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
Type Values Removed Values Added
First Time appeared Openemr
Openemr openemr
Vendors & Products Openemr
Openemr openemr
Type Values Removed Values Added
Description 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 optional FaxSMS module (`oe-module-faxsms`) allows any authenticated OpenEMR user to invoke controller methods — including `getNotificationLog()`, which returns patient appointment data (PHI) — regardless of whether they hold the required ACL permissions. The `AppDispatch` constructor dispatches user-controlled actions and exits the process before any calling code can enforce ACL checks. Version 8.0.0.2 fixes the issue.
Title OpenEMR has Authorization Bypass in FaxSMS AppDispatch Constructor
Weaknesses CWE-696
CWE-862
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 21, 2026, 3:31 AM
Reserved
Mar 18, 2026, 6:55 PM
Status
Analyzed
Published
Mar 19, 2026, 9:17 PM
Modified
Jun 17, 2026, 10:37 AM