CVE-2026-24848
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 · uneditedOpenEMR is a free and open source electronic health records and medical practice management application. In 7.0.4 and earlier, the disposeDocument() method in EtherFaxActions.php allows authenticated users to write arbitrary content to arbitrary locations on the server filesystem. This vulnerability can be exploited to achieve Remote Code Execution (RCE) by uploading malicious PHP web shells.
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 confidenceThe disposeDocument() method in EtherFaxActions.php in OpenEMR 7.0.4 and earlier lacks proper path validation, allowing authenticated users to write arbitrary content to any location on the server filesystem via path traversal. This arbitrary file write capability can be chained with uploading PHP web shells to achieve remote code execution.
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< 7.0.4CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Check OpenEMR versionLocate the version file or admin interface to determine the installed OpenEMR version. Common locations include a VERSION file in the root directory or the admin > System > Info page.Affected if The installed version is any version prior to 7.0.4 (e.g., 7.0.3, 7.0.2, 7.0.1, 7.0.0, or earlier releases).
-
Verify EtherFax module statusCheck if the EtherFax module is enabled in the OpenEMR administration panel under Modules or Features configuration, or inspect the modules directory for EtherFax-related files.Affected if The EtherFax module is installed and enabled, making the vulnerable disposeDocument() method accessible to authenticated users.
-
Review access logs for EtherFax endpointSearch web server access logs for requests to EtherFaxActions.php, particularly POST requests that may indicate document disposal operations.Affected if Logs show POST requests to disposeDocument or similar endpoints from untrusted user accounts.
-
Audit filesystem for unexpected file creationsCheck web-accessible directories (especially the main OpenEMR web root, tmp, and custom modules folders) for newly created PHP files with suspicious names or contents.Affected if Unexpected PHP files are found, especially in directories where users should not have write access, which may indicate successful exploitation.
You are affected if running any OpenEMR version prior to 7.0.4 with the EtherFax module enabled, or if evidence of unauthorized file creation via EtherFaxActions.php is found in logs or on the filesystem.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.0.4
Upgrade to a patched version of OpenEMR. Until then, restrict access to the EtherFax functionality to trusted users only, disable the EtherFax module if not required, and monitor for suspicious file creation activity.
OpenEMR 7.0.4 or later
- Verify current OpenEMR version by checking the admin interface or looking at version.php in the web root
- Download OpenEMR version 7.0.4 or later from the official repository (github.com/openemr/openemr)
- Create a complete backup of the OpenEMR database and filesystem before proceeding
- Review the upgrade instructions in the OpenEMR wiki or INSTALL file
- Upload and extract the new version files, or use the built-in patcher if available
- Run database upgrade scripts if included in the release
- Verify the upgrade was successful by checking the version number
- Confirm the EtherFaxActions.php file has been updated and no longer contains the path traversal vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24848 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24848 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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