<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>OpenEMR (&lt; 8.3.0) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/openemr--8.3.0/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sun, 08 Nov 2026 21:26:25 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/openemr--8.3.0/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>OpenEMR: SQL injection in Fee Sheet drug-inventory lookup (CVE-2026-124469)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-sqli/</link><pubDate>Sun, 08 Nov 2026 21:26:25 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-sqli/</guid><description>OpenEMR versions prior to 8.3.0 are susceptible to time-based blind SQL injection in the Fee Sheet component, allowing low-privileged authenticated users to exfiltrate patient data and user hashes.</description><content:encoded><![CDATA[<p>OpenEMR versions before 8.3.0 contain an SQL injection vulnerability in the <code>DrugSalesService::sellDrug</code> method. The vulnerability arises from improper sanitization of the <code>prod[N][warehouse]</code> POST field before it is used in an <code>ORDER BY</code> clause. An authenticated attacker with low privileges can leverage this flaw to perform time-based blind SQL injection attacks to exfiltrate sensitive data, such as patient records and bcrypt hashes of user credentials.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows authenticated attackers to perform unauthorized data extraction, leading to the compromise of patient PII and user authentication data (bcrypt hashes).</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade to OpenEMR version 8.3.0 or later to address the vulnerability.</li>
<li>Audit access logs for abnormal POST request patterns to the <code>DrugSalesService</code> or Fee Sheet-related endpoints containing SQL injection syntax, particularly within the <code>prod[N][warehouse]</code> parameter.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>web-application</category><category>sql-injection</category><category>health-sector</category></item><item><title>OpenEMR: Insecure direct object reference in portal/lib/persist.php (CVE-2026-124453)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-idor-4ecb7d2c/</link><pubDate>Sun, 08 Nov 2026 19:33:41 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-idor-4ecb7d2c/</guid><description>OpenEMR versions before 8.3.0 contain an insecure direct object reference vulnerability in portal/lib/persist.php that allows authenticated portal patients to write settings for other patients.</description><content:encoded>&lt;p>OpenEMR before 8.3.0 contains an insecure direct object reference vulnerability in portal/lib/persist.php. Authenticated portal patients can modify the setting_patient parameter in a JSON POST request to another patient's PID, allowing them to alter that patient's portal settings, such as the portal theme.&lt;/p>
</content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>OpenEMR: Missing authorization in billing module (CVE-2026-124471)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-auth-bypass-dbd20544/</link><pubDate>Sun, 08 Nov 2026 17:30:44 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-auth-bypass-dbd20544/</guid><description>OpenEMR versions prior to 8.3.0 contain an authorization bypass in the sl_eob_invoice.php script that allows authenticated users to read and modify arbitrary billing records via parameter manipulation.</description><content:encoded><![CDATA[<p>OpenEMR versions prior to 8.3.0 are vulnerable to a missing authorization flaw in 'interface/billing/sl_eob_invoice.php'. The vulnerability allows an authenticated user to perform unauthorized operations by manipulating the 'id' parameter in HTTP requests. Impacted operations include reading patient names and billing notes, posting payments, applying adjustments, and deleting billing entries for any encounter regardless of the user's assigned permissions.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows for unauthorized data disclosure (PII/PHI) and modification of financial and clinical billing records across all patient encounters.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenEMR to version 8.3.0 or later to remediate CVE-2026-124471.</li>
<li>Audit access logs for the 'interface/billing/sl_eob_invoice.php' endpoint to identify patterns of excessive or abnormal requests to the 'id' parameter by non-billing personnel.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>OpenEMR: Stored Cross-Site Scripting (CVE-2026-124463)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-xss-0acba206/</link><pubDate>Sun, 08 Nov 2026 17:30:33 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-xss-0acba206/</guid><description>OpenEMR versions prior to 8.3.0 contain a stored cross-site scripting vulnerability allowing authenticated users with CAMOS access to execute arbitrary scripts in a victim context.</description><content:encoded><![CDATA[<p>OpenEMR versions before 8.3.0 contain a stored cross-site scripting (XSS) vulnerability. Authenticated users with CAMOS (Computerized Assisted Medical Office Suite) access can inject malicious HTML or scripts by saving content through the <code>ajax_save.php</code> endpoint. The payload is subsequently executed when a victim accesses the entry via the <code>rx_print.php</code> script (specifically the non-print_html branch), allowing the attacker to perform actions or read data as the authenticated user.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows authenticated attackers to perform unauthorized actions or exfiltrate sensitive data by executing scripts within the browser session of a victim user who views the malicious content.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenEMR to version 8.3.0 or later to remediate the vulnerability.</li>
<li>Audit access controls for the CAMOS module to ensure only trusted users have the ability to save content.</li>
<li>Monitor web server logs for suspicious POST requests to <code>ajax_save.php</code> containing script-related characters.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>xss</category><category>web-application</category><category>medical-software</category></item><item><title>OpenEMR: Arbitrary file read and write vulnerability (CVE-2026-124450)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-path-traversal-803ffbda/</link><pubDate>Sun, 08 Nov 2026 16:50:56 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-path-traversal-803ffbda/</guid><description>OpenEMR versions prior to 8.3.0 are vulnerable to path traversal in the fax/sms module, allowing authenticated attackers to read sensitive files and execute arbitrary code via file write.</description><content:encoded><![CDATA[<p>OpenEMR versions prior to 8.3.0 contain a broken access control and path traversal vulnerability in the fax/sms module's 'disposeDocument' action. The vulnerability stems from an unvalidated 'file_path' parameter, which allows authenticated, low-privileged users to perform arbitrary file reads (including the retrieval of database credentials from 'sqlconf.php') and arbitrary file writes as the web service user, ultimately leading to remote code execution.</p>
<h2 id="impact">Impact</h2>
<p>Authenticated low-privilege users can recover database credentials, modify application configuration, or achieve remote code execution on the underlying server as the web service user.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Patch OpenEMR to version 8.3.0 or later immediately to resolve the vulnerability.</li>
<li>Audit access logs for authentication-related activity followed by suspicious requests to the 'fax/sms' module.</li>
<li>Monitor for unauthorized file modification in the OpenEMR web directory.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>cve-2026-124450</category><category>path-traversal</category><category>rce</category><category>webserver</category></item><item><title>OpenEMR: Broken access control in portal_payment.php (CVE-2026-124489)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-broken-access-control/</link><pubDate>Sun, 08 Nov 2026 15:36:54 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-broken-access-control/</guid><description>OpenEMR versions prior to 8.3.0 are vulnerable to broken access control, allowing authenticated, low-privileged users to modify patient identifiers to bypass billing restrictions and record fraudulent payments.</description><content:encoded><![CDATA[<p>OpenEMR versions before 8.3.0 contain a broken access control vulnerability in the <code>portal/portal_payment.php</code> script. An authenticated attacker with low privileges can bypass billing access control list (ACL) checks by manipulating the <code>pid</code> and <code>form_pid</code> parameters in requests. This allows unauthorized access to patient payment pages and the submission of fraudulent payment receipts, resulting in billing data corruption.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthorized users to view sensitive payment data of arbitrary patients and inject fraudulent payment records into the system, compromising the integrity of financial billing records.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenEMR to version 8.3.0 or later immediately to patch the access control vulnerability in <code>portal_payment.php</code>.</li>
<li>Audit billing records for entries created by low-privilege accounts, specifically looking for irregularities in <code>pid</code> and <code>form_pid</code> parameter associations.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>OpenEMR: Missing authorization in patient recall records (CVE-2026-124477)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-auth-bypass-c78c243c/</link><pubDate>Sun, 08 Nov 2026 15:36:08 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-auth-bypass-c78c243c/</guid><description>OpenEMR versions prior to 8.3.0 are vulnerable to an authorization bypass allowing authenticated, low-privileged users to delete arbitrary patient recall records via the delete_Recall action.</description><content:encoded><![CDATA[<p>OpenEMR versions before 8.3.0 contain a missing authorization vulnerability (CVE-2026-124477) that allows low-privileged authenticated users to delete arbitrary patient recall records. The vulnerability is triggered by sending a POST request to <code>/interface/main/messages/save.php</code> with the <code>delete_Recall</code> action, targeting a specific patient ID (pid) and record ID (r_ID). The application fails to perform necessary Access Control List (ACL) or ownership checks before processing the deletion, leading to unauthorized data loss.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows an authenticated attacker to delete patient recall data, potentially causing medical records disruption or data loss.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenEMR to version 8.3.0 or later immediately to resolve the missing authorization check.</li>
<li>Audit access logs for unauthorized access or execution of the <code>delete_Recall</code> action by low-privileged user accounts.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>OpenEMR: Broken object-level authorization in SOAP note API (CVE-2026-124473)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-bola/</link><pubDate>Sun, 08 Nov 2026 15:35:53 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-bola/</guid><description>OpenEMR versions prior to 8.3.0 contain a broken object-level authorization vulnerability that allows authenticated users to overwrite clinical notes belonging to other patients by manipulating the SOAP note ID in API requests.</description><content:encoded><![CDATA[<p>OpenEMR versions prior to 8.3.0 contain a broken object-level authorization (BOLA) vulnerability in the SOAP note update API. The application fails to verify that the provided SOAP note ID (sid) is associated with the patient and encounter specified in the request URI. An authenticated user with existing &quot;encounters/notes&quot; permissions can perform a PUT request to the API, allowing them to overwrite existing clinical notes and reassign the records to a different patient ID.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation results in unauthorized modification of clinical records and data integrity compromise within the electronic medical record system.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenEMR to version 8.3.0 or later to resolve the underlying authorization logic flaw.</li>
<li>Audit web server logs for PUT requests to the SOAP note API where the requested Patient ID (pid) or Encounter ID (eid) may be inconsistent with access patterns or user-specific permissions.</li>
<li>Review access control logs for users with &quot;encounters/notes&quot; permissions to identify anomalous update activity.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>OpenEMR: Missing authorization in billing notes (CVE-2026-124472)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-auth-bypass-37ec9377/</link><pubDate>Sun, 08 Nov 2026 15:35:35 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-auth-bypass-37ec9377/</guid><description>OpenEMR versions prior to 8.3.0 are vulnerable to a missing authorization flaw allowing authenticated low-privileged users to read and modify sensitive patient billing notes via parameter manipulation.</description><content:encoded><![CDATA[<p>OpenEMR versions before 8.3.0 contain a missing authorization vulnerability in the script 'interface/billing/sl_eob_patient_note.php'. This vulnerability enables an authenticated user to perform unauthorized read and modification operations on patient billing notes. By manipulating the 'patient_id' parameter in HTTP POST requests and reusing legitimate CSRF tokens, a low-privilege attacker can access confidential data belonging to other patients.</p>
<h2 id="impact">Impact</h2>
<p>The vulnerability allows unauthorized access to and tampering with patient billing records, which constitutes a significant compromise of protected health information (PHI) and data integrity within the OpenEMR instance.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenEMR to version 8.3.0 or later immediately to remediate the missing authorization check.</li>
<li>Review application access logs for anomalous POST request patterns directed at 'sl_eob_patient_note.php', specifically where the 'patient_id' parameter varies rapidly or is accessed by accounts that lack administrative or billing roles.</li>
<li>Audit user permissions and ensure that Principle of Least Privilege is applied to all clinical and billing staff accounts to limit the blast radius of compromised credentials.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>OpenEMR: Missing authorization in document upload (CVE-2026-124461)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-auth-bypass-a575c508/</link><pubDate>Sun, 08 Nov 2026 15:34:30 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-auth-bypass-a575c508/</guid><description>OpenEMR versions prior to 8.3.0 are susceptible to an authorization bypass vulnerability allowing authenticated users to read and overwrite arbitrary document data via the library/ajax/upload.php script.</description><content:encoded><![CDATA[<p>OpenEMR versions prior to 8.3.0 contain a missing authorization vulnerability in 'library/ajax/upload.php'. This flaw permits an authenticated user to perform unauthorized read and write operations on document data by manipulating the 'doc_id' parameter.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows low-privileged users to enumerate document IDs, leading to the unauthorized disclosure of patient health information (PHI) and the potential tampering of medical records across the entire installation.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenEMR to version 8.3.0 or later to remediate the authorization logic flaw.</li>
<li>Implement strict access control monitoring for requests directed to 'library/ajax/upload.php'.</li>
<li>Review application access logs for abnormal volumes of requests to the document upload endpoint, specifically those targeting sequential or unusual 'doc_id' values.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>web-application-vulnerability</category><category>authorization-bypass</category><category>health-sector</category></item><item><title>OpenEMR: Insecure Direct Object Reference in encounter-form endpoints (CVE-2026-124459)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-idor-db815b70/</link><pubDate>Sun, 08 Nov 2026 15:32:29 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-idor-db815b70/</guid><description>OpenEMR versions prior to 8.3.0 are susceptible to an Insecure Direct Object Reference (IDOR) vulnerability that allows authenticated users to access and modify clinical records belonging to other patients by enumerating form IDs.</description><content:encoded><![CDATA[<p>OpenEMR versions before 8.3.0 contain an insecure direct object reference (IDOR) vulnerability in multiple encounter-form view and save endpoints. These endpoints fail to perform patient or encounter ownership validation checks. An authenticated clinical user can leverage this by incrementing sequential form ID values within HTTP requests to view or overwrite clinical data belonging to other patients.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows an authenticated attacker to read sensitive clinical records and modify or overwrite medical data belonging to other patients, leading to potential data corruption and unauthorized information disclosure.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenEMR to version 8.3.0 or later immediately to patch the missing ownership checks.</li>
<li>Restrict access to clinical form endpoints for non-clinical user roles if the update cannot be applied immediately.</li>
<li>Implement granular auditing of access to encounter-form endpoints to identify anomalous enumeration patterns.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>OpenEMR: Missing authorization and IDOR in oe-module-prior-authorizations (CVE-2026-124456)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-idor-f0a19413/</link><pubDate>Sun, 08 Nov 2026 15:32:12 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-idor-f0a19413/</guid><description>OpenEMR versions before 8.3.0 contain IDOR and authorization flaws in the oe-module-prior-authorizations module that allow authenticated users to access and modify patient records.</description><content:encoded><![CDATA[<p>OpenEMR versions prior to 8.3.0 contain missing authorization and insecure direct object reference (IDOR) vulnerabilities within the <code>oe-module-prior-authorizations</code> module. These flaws allow an authenticated low-privilege user to access and manipulate sensitive patient data, including patient names, medical record numbers (MRNs), insurance details, and prior-authorization records.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows for unauthorized disclosure of Protected Health Information (PHI) and unauthorized modification of patient prior-authorization records.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenEMR to version 8.3.0 or later to apply the security fixes.</li>
<li>Restrict user access to the <code>oe-module-prior-authorizations</code> module if immediate patching is not feasible.</li>
<li>Monitor access logs for requests to <code>public/reports/list_report.php</code> and <code>public/index.php</code> that deviate from expected behavioral patterns for low-privilege user accounts.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>OpenEMR: Stored cross-site scripting in CCDA/CCD preview (CVE-2026-124448)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-xss/</link><pubDate>Sun, 08 Nov 2026 15:31:55 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-xss/</guid><description>OpenEMR versions before 8.3.0 are vulnerable to stored cross-site scripting via maliciously crafted CCDA/CCD document attachments that execute scripts in a clinician's session upon preview.</description><content:encoded><![CDATA[<p>OpenEMR versions prior to 8.3.0 contain stored cross-site scripting (XSS) vulnerabilities within the CCDA/CCD preview stylesheets. Specifically, the cda.xsl and ccd.xsl files fail to properly sanitize input, allowing event-handler attributes such as onmouseover, onclick, and onfocus to be injected into previewed HTML. An authenticated attacker can upload a crafted CCDA/CCD document containing these malicious handlers to execute unauthorized JavaScript in the context of a clinician's session.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows authenticated attackers to execute arbitrary JavaScript within a clinician's session, potentially leading to unauthorized data access, session hijacking, or other actions performed with the clinician's privileges within the OpenEMR application.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenEMR to version 8.3.0 or later to apply the fix for CVE-2026-124448.</li>
<li>Implement Content Security Policy (CSP) headers that restrict inline script execution to reduce the impact of XSS vulnerabilities.</li>
<li>Audit access logs for user accounts uploading CCDA/CCD documents to identify potential abuse of the file upload functionality.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>xss</category><category>web-application-vulnerability</category><category>health-sector</category></item><item><title>OpenEMR: Insecure direct object reference in OnsitePortalActivityController (CVE-2026-124447)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-idor/</link><pubDate>Sun, 08 Nov 2026 15:31:47 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-idor/</guid><description>OpenEMR versions prior to 8.3.0 contain an Insecure Direct Object Reference vulnerability in the OnsitePortalActivityController::Update() function that allows authenticated portal patients to access, modify, and assume ownership of records belonging to other patients.</description><content:encoded><![CDATA[<p>OpenEMR versions before 8.3.0 are susceptible to an Insecure Direct Object Reference (IDOR) vulnerability located in the <code>OnsitePortalActivityController::Update()</code> function. The application fails to validate whether the authenticated patient ID matches the record owner ID. An attacker with a valid patient portal account can manipulate PUT requests to the <code>onsiteportalactivity</code> API by specifying arbitrary activity IDs alongside their own patient ID. This leads to the unauthorized disclosure of <code>tableArgs</code> and <code>checksum</code> data, as well as the ability to overwrite activity narratives and status, effectively allowing the attacker to assume ownership of another patient's medical activity records.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthorized disclosure of sensitive medical activity data, modification of existing record narratives and status fields, and account-level record takeover within the OpenEMR patient portal.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenEMR to version 8.3.0 or later to include the fix for CVE-2026-124447.</li>
<li>Audit web server logs for suspicious PUT requests to the <code>onsiteportalactivity</code> API endpoint, specifically monitoring for instances where the authenticated user ID is linked to record IDs that do not belong to that session context.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>OpenEMR: Path traversal in RingCentral RCFaxClient (CVE-2026-124490)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openemr-path-traversal/</link><pubDate>Sun, 08 Nov 2026 15:29:19 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openemr-path-traversal/</guid><description>OpenEMR versions prior to 8.3.0 are vulnerable to path traversal within the RingCentral RCFaxClient disposeDocument() method, enabling authenticated attackers to read arbitrary files or achieve remote code execution via file writes.</description><content:encoded><![CDATA[<p>OpenEMR versions before 8.3.0 contain a path traversal vulnerability in the RingCentral RCFaxClient disposeDocument() method of the oe-module-faxsms component. An authenticated attacker can exploit the file_path parameter to read sensitive files, such as configuration files containing credentials or source code. Furthermore, an attacker can use the action=setup parameter with base64-encoded content to write web-executable files, leading to remote code execution.</p>
<h2 id="impact">Impact</h2>
<p>The vulnerability allows authenticated attackers to perform unauthorized file system reads and writes, resulting in potential exposure of sensitive data (credentials/source code) and full system compromise via remote code execution.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenEMR to version 8.3.0 or later immediately to resolve the vulnerable disposeDocument() method.</li>
<li>Audit web server access logs for requests directed at the oe-module-faxsms component containing path traversal patterns (e.g., ../, ..).</li>
<li>Review user access privileges for the OpenEMR instance to limit exposure to authenticated session exploitation.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category></item></channel></rss>