dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-46823

HIGH · 8.0 CVSS v4.0 Published 2025-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The FHIR2 module for OpenMRS had incomplete privilege/authorization checks in its REST API, allowing unauthorized users to add or edit medical data they should not have access to. This is an authorization bypass vulnerability in a healthcare data system.

MitigationUpdate the openmrs-module-fhir2 to version 2.5.0 or newer to receive the privilege checking patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if FHIR2 module is installed
    In OpenMRS admin interface, go to Manage Modules or check the /openmrs/modules directory for fhir2 module files. Alternatively, query the module table in the database or check the system information page for loaded modules.
    Affected if The FHIR2 module (openmrs-module-fhir2) is present in the OpenMRS instance
  2. Check FHIR2 module version
    In OpenMRS admin, view the FHIR2 module details page to see the installed version number. This is typically displayed on the module information or system information screen.
    Affected if The installed version is lower than 2.5.0 (the patched version)
  3. Verify REST API endpoints are exposed
    Check if the FHIR2 REST endpoints are accessible by attempting to reach endpoints such as /openmrs/ws/fhir2/{resource} (e.g., /ws/fhir2/Patient or /ws/fhir2/Observation) from an unauthorized or untrusted account.
    Affected if FHIR2 REST endpoints are accessible without proper authentication or from untrusted user accounts
  4. Confirm user authorization controls
    Test creating or modifying medical data (such as Observations, Conditions, or Patient resources) using a user account that should NOT have privileges to access that specific patient's data. Use the POST/PUT methods on the FHIR2 endpoints.
    Affected if An unauthorized user can successfully add or edit medical data they should not have access to via the FHIR2 REST API

A user is affected if the FHIR2 module is installed and its version is below 2.5.0, and the REST API allows unauthorized access to medical data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the openmrs-module-fhir2 to version 2.5.0 or newer to receive the privilege checking patch.

Recommended fix High confidence

FHIR2 module version 2.5.0 or newer

  1. 1. Back up your current OpenMRS database and configuration
  2. 2. Download the FHIR2 module version 2.5.0 or newer from the OpenMRS module repository (https://modules.openmrs.org)
  3. 3. Log in to the OpenMRS Administration interface
  4. 4. Navigate to the 'Manage Modules' page
  5. 5. Stop the currently running FHIR2 module if it is active
  6. 6. Uninstall the existing FHIR2 module
  7. 7. Install the new FHIR2 module version 2.5.0 or newer
  8. 8. Verify the module starts successfully
Caveat Review the FHIR2 module 2.5.0 release notes for any changes to REST API behavior or data formats that may affect existing integrations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46823 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46823 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data