dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 10 Jun 2024. Known ransomware use
Mirth ConnectApplication · Nextgen

CVE-2023-43208

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-26
Fix available
A fix is available. Upgrade to 4.4.1 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit 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
NextGen Healthcare Mirth Connect before version 4.4.1 is vulnerable to unauthenticated remote code execution. Note that this vulnerability is caused by the incomplete patch of CVE-2023-37679.

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 · moderate confidence

NextGen Healthcare Mirth Connect versions before 4.4.1 contain an unauthenticated remote code execution vulnerability resulting from an incomplete patch for CVE-2023-37679, allowing attackers to execute arbitrary code without authentication.

MitigationUpgrade Mirth Connect to version 4.4.1 or later immediately; given the CVSS 9.8 severity and unauthenticated attack vector, this should be prioritized as an emergency patch.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mirth ConnectApplication
Affected:< 4.4.1

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Locate Mirth Connect installation directory
    Identify the server where Mirth Connect is installed. Common installation paths include C:\Program Files\Mirth\Mirth Connect (Windows) or /opt/mirthconnect (Linux). Check for the mirth.properties file or version.xml in the installation folder.
    Affected if Installation directory cannot be found or the application is not installed on the expected system.
  2. Determine installed Mirth Connect version
    Open the admin web interface and navigate to the About section, or check the version file in the installation directory (version.txt, version.properties, or the manifest). Alternatively, examine the mirth.properties file for version metadata.
    Affected if The displayed or recorded version number is lower than 4.4.1.
  3. Compare version to CVE threshold
    Document the exact version number found (for example, 4.4.0, 4.3.1, etc.) and compare it against the affected range: any version prior to 4.4.1.
    Affected if The installed version is 4.4.0 or any earlier release (e.g., 4.3.x, 4.2.x).
  4. Verify administrative interface accessibility
    Confirm whether the Mirth Connect admin web interface (default ports 8080 or 8443) is reachable from network segments that are not trusted or are externally accessible. Use a browser or curl to test http://hostname:8080/admin or https://hostname:8443/admin.
    Affected if The admin interface is exposed to untrusted networks without authentication restrictions.
  5. Review logs for unauthorized access attempts
    Examine Mirth Connect server logs (located in the logs folder within the installation directory) for suspicious requests, especially to endpoints that may execute code or scripts, around the time of potential exploitation.
    Affected if Logs show unexpected requests to administrative functions from unknown IP addresses or unusual execution patterns.

You are affected if your installed Mirth Connect version is lower than 4.4.1 AND the administrative interface is network-accessible.

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
Upgrade available Upgrade to 4.4.1 or later
Fixed in 4.4.1
Interim mitigation

Upgrade Mirth Connect to version 4.4.1 or later immediately; given the CVSS 9.8 severity and unauthenticated attack vector, this should be prioritized as an emergency patch.

Recommended fix High confidence

4.4.1

  1. Download Mirth Connect version 4.4.1 or later from the official NextGen Healthcare vendor site
  2. Create a complete backup of the current Mirth Connect installation directory
  3. Back up the Mirth Connect database
  4. Stop the Mirth Connect service
  5. Install or upgrade to Mirth Connect version 4.4.1
  6. Start the Mirth Connect service
  7. Verify the version upgrade was successful by checking the About page in the admin console
Caveat Review NextGen Healthcare release notes for any configuration or compatibility changes before upgrading

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

Fix this in Mirth Connect Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-43208 — 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-2023-43208 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