VulnerabilityPublished 29 May 2025

CVE-2025-46823: openmrs-module-fhir2 · Missing Authorization

Affects openmrs-module-fhir2Source CVE Database V5

Not known to be exploited · CVSS 8.0 High : upgrade to 2.5.0 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

8.0High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.5.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: Unreported

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: Unreported: Based on threat intelligence sources each of the following must apply: · No knowledge of publicly available proof-of-concept · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade openmrs/openmrs-module-fhir2 to 2.5.0.

Affected software

Product	Affected	Fixed in
GitHubopenmrs/openmrs-module-fhir2`pkg:github/openmrs/openmrs-module-fhir2`Other threats	Affected <2.5.0	Fixed in 2.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations using OpenMRS should prioritize upgrading the openmrs-module-fhir2 to version 2.5.0 or later immediately to apply the official patch that corrects the authorization checks. In addition to patching, organizations should implement strict network segmentation to isolate healthcare systems from general-purpose networks and the internet, reducing exposure. Deploying Web Application Firewalls (WAFs) with rules tailored to detect anomalous FHIR API requests can provide an additional layer of defense. Regular auditing and monitoring of API access logs should be instituted to detect unauthorized access attempts or suspicious modifications. Organizations should also enforce strong access control policies, including multi-factor authentication for administrative interfaces and API endpoints where feasible. Conducting security awareness training for IT staff on the importance of timely patch management and monitoring for vulnerabilities in healthcare software is critical. Finally, organizations should have an incident response plan tailored to healthcare data breaches, ensuring rapid containment and remediation if exploitation occurs.

Description

openmrs-module-fhir2 provides the FHIR REST API and related services for OpenMRS, an open medical records system. In versions of the FHIR2 module prior to 2.5.0, privileges were not always correctly checked, which means that unauthorized users may have been able to add or edit data they were not supposed to be able to. All implementers should update to FHIR2 2.5.0 or newer as soon as is feasible to receive a patch.

Impact

For European organizations, particularly healthcare providers, this vulnerability poses a significant risk. Unauthorized modification or addition of patient records can lead to incorrect medical treatments, diagnostic errors, and compromised patient safety. Additionally, breaches of patient data confidentiality can result in violations of the EU General Data Protection Regulation (GDPR), leading to substantial legal and financial penalties. The integrity loss of medical records undermines trust in healthcare systems and can disrupt clinical workflows. Given that OpenMRS is used in various public health institutions and NGOs across Europe, exploitation could affect a broad range of entities, from hospitals to research institutions. The remote, unauthenticated nature of the vulnerability means attackers could potentially exploit it from outside the network perimeter, increasing the threat surface. Moreover, the absence of known exploits does not diminish the urgency, as the vulnerability is straightforward to exploit and could be targeted by opportunistic attackers or advanced persistent threat actors aiming to disrupt healthcare services or steal sensitive data.

Summary

CVE-2025-46823 is a high-severity vulnerability identified in the openmrs-module-fhir2, a module that provides FHIR (Fast Healthcare Interoperability Resources) REST API services for OpenMRS, an open-source medical records system widely used in healthcare environments. The vulnerability is classified under CWE-862, which pertains to missing authorization. Specifically, in versions of the FHIR2 module prior to 2.5.0, the system failed to consistently enforce privilege checks. This flaw allows unauthorized users to add or modify medical data via the FHIR API without proper permissions. Since OpenMRS is designed to manage sensitive patient information, unauthorized data manipulation can lead to significant confidentiality and integrity breaches. The vulnerability is remotely exploitable over the network without requiring authentication or user interaction, increasing the risk of exploitation. The CVSS 4.0 base score of 8.0 reflects the critical nature of the vulnerability, highlighting high impact on confidentiality and integrity, with low attack complexity and no privileges or user interaction needed. Although no known exploits are currently reported in the wild, the potential for abuse is substantial given the sensitive nature of healthcare data and the widespread use of OpenMRS in various healthcare institutions globally. The recommended remediation is to upgrade the openmrs-module-fhir2 to version 2.5.0 or later, where the authorization checks have been properly implemented to prevent unauthorized access and modification of data.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 22:55 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats