Security readout for executives and security teams
Plain-English summary
OpenEMR versions before 8.0.0 can let a user with a patient-scoped FHIR token view CareTeam information beyond that patient. In a healthcare setting, this may expose Protected Health Information such as patient-provider relationships and care team structures. The issue is patched in OpenEMR 8.0.0.
Executive priority
Prioritize remediation for healthcare environments using OpenEMR FHIR APIs, especially where patient applications or integrations receive patient-scoped tokens. The issue can expose PHI across the system, creating privacy and compliance risk, but available sources do not indicate active exploitation.
Technical view
The FHIR CareTeam resource endpoint does not enforce patient compartment filtering correctly. The advisory states FhirCareTeamService lacks IPatientCompartmentResourceService implementation and does not pass the patient binding parameter to the underlying service. This allows patient-scoped FHIR tokens to retrieve CareTeam data across patients. CVSS v4.0 score is 5.7.
Likely exposure
Exposure is limited to OpenEMR deployments before 8.0.0 with FHIR enabled and patient-scoped FHIR token access. The main impact is confidentiality loss, not system compromise or data modification, based on the provided CVSS and advisory details.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not state active exploitation. The CVSS vector includes low attack complexity and required low privileges, meaning misuse may be practical for someone already holding a patient-scoped FHIR token.
Researcher notes
Focus review on FHIR authorization enforcement for CareTeam resources in OpenEMR before 8.0.0. The root cause is missing patient compartment integration in FhirCareTeamService. Validate only with authorized test data and avoid broad PHI retrieval during assessment.
Mitigation direction
- Upgrade OpenEMR to version 8.0.0 or later.
- Review OpenEMR advisory GHSA-4frq-f657-hwrc for vendor guidance.
- Restrict FHIR token issuance to necessary users and applications.
- Review access logs for unusual CareTeam resource queries.
Validation and detection
- Identify all OpenEMR instances and confirm their versions.
- Confirm whether FHIR APIs are enabled on each instance.
- Verify patient-scoped tokens cannot access other patients' CareTeam records.
- Check audit logs for broad CareTeam access using patient-scoped tokens.
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-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-24487 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
- 5.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
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:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
5.7MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/openemr/openemr/security/advisories/GHSA-4frq-f657-hwrcCVE reference · x_refsource_CONFIRM
- https://github.com/openemr/openemr/commit/5ce10a3961b73862aaf31eb30044ffe1018465ccCVE 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.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.