Security readout for executives and security teams
Plain-English summary
OpenEMR versions up to 8.0.0 can let any logged-in user send server files out through the fax feature. This could expose database credentials, patient documents, system files, or source code. The issue is serious for healthcare privacy, but the cited severity is medium because the attacker needs an authenticated account.
Executive priority
Treat as priority remediation for OpenEMR environments holding patient data. The business risk is confidentiality loss through an ordinary authenticated account. If fax features are unused, disabling them can reduce exposure while waiting for vendor guidance.
Technical view
The fax sending endpoint accepts user-supplied file paths and streams referenced files to the fax gateway without path restrictions or authorization checks. The advisory classifies this as CWE-22 with CVSS 3.1 score 6.5. Affected OpenEMR versions are listed as up to and including 8.0.0, with no known patched version at publication.
Likely exposure
Organizations running OpenEMR <= 8.0.0 with the fax/SMS module or fax sending workflow enabled are potentially exposed. Risk is higher where many users have accounts, shared accounts exist, or fax egress is unrestricted.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not marked KEV. Exploitation requires network access to OpenEMR and valid authentication, then abuse of the fax endpoint’s file path handling to transmit server-readable files.
Researcher notes
Evidence comes from the GitHub advisory and referenced OpenEMR source path. The advisory states arbitrary file exfiltration through the fax endpoint and no known patched versions at publication. Do not assume unauthenticated exposure or active exploitation from the supplied data.
Mitigation direction
- Check the OpenEMR advisory and vendor channels for patched versions or official workarounds.
- Restrict fax functionality to the smallest necessary set of trusted users.
- Disable fax/SMS functionality or outbound fax gateway access if not operationally required.
- Review account hygiene; remove unused users and shared credentials.
- Monitor fax activity for unusual destinations, filenames, or high-volume transmissions.
Validation and detection
- Inventory OpenEMR instances and confirm whether versions are <= 8.0.0.
- Determine whether the oe-module-faxsms or EtherFax workflow is installed and enabled.
- Review role assignments for users allowed to access fax sending features.
- Inspect fax gateway logs for unexpected recipient numbers or unusual file references.
- Track the GitHub advisory for confirmation of a fixed release.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24488 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/openemr/openemr/security/advisories/GHSA-765x-8v97-c7g8CVE reference · x_refsource_CONFIRM
- https://github.com/openemr/openemr/blob/v7_0_4/interface/modules/custom_modules/oe-module-faxsms/src/Controller/EtherFaxActions.php#L177-L221CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.