FrankenPHP standalone static binaries from version 1.8.0 up to but not including 1.13.2 include a statically linked PHP brotli extension with Brotli 1.2.0. This version of Brotli contains an out-of-bounds write vulnerability (CVE-2026-111497) in its decoder. Unauthenticated remote attackers can exploit this by sending crafted data to applications that use brotli_uncompress_add(), potentially causing the FrankenPHP process to crash and possibly leading to memory disclosure or code execution.
FrankenPHP versions prior to 1.13.4 have a use-after-free vulnerability in worker mode involving internal streams of SplTempFileObject or SplFileObject on php://temp instances that persist across requests. This flaw allows remote clients to trigger reads of freed memory, potentially leaking garbage data or causing process crashes.
FrankenPHP versions prior to 1.13.4 have an information disclosure vulnerability in worker mode where environment variables from one request can leak into subsequent requests on the same PHP thread. This allows attackers to access sensitive per-request environment data such as routing, tenant, or authorization values via getenv() or $_SERVER, potentially causing unauthorized application behavior.
OpenEMR versions prior to 8.5.0 have a second-order SQL injection vulnerability in the IPPF contraceptive issue feature. This occurs because the issue_ippf_con_save function concatenates user-controlled field_id values into a SQL REPLACE INTO query as column names. Authenticated administrators can exploit this by adding a malicious field_id via edit_layout.php and then triggering the vulnerable function through add_edit_issue.php, allowing arbitrary SQL execution.
OpenEMR versions prior to 8.5.0 contain a second-order SQL injection vulnerability that allows low-privileged authenticated users to inject malicious SQL code. The vulnerability arises from the ability to store a SQL fragment in the recent_patient_columns option_id value via library/ajax/addlistitem.php, which is later concatenated and executed in dynamic_finder.php. This flaw can lead to high confidentiality impact by exposing sensitive data.
OpenEMR versions prior to 8.5.0 contain active debug code in the interface/fax/fax_view.php file that executes the passthru("groups") command. This causes disclosure of the web server's Unix group memberships. Authenticated users with access to the fax module can exploit this by supplying a nonexistent jid value to reveal sensitive group information such as adm or shadow, which could assist in planning privilege escalation attacks.
OpenEMR versions prior to 8.5.0 contain an SQL injection vulnerability in the SLEOB::slInvoiceNumber() function within src/Billing/SLEOB.php. This vulnerability arises because the CLP01 claim identifier from uploaded X12 835 ERA files is concatenated directly into an SQL query without proper escaping or parameter binding. Authenticated users with billing permissions or malicious payers whose ERA files are uploaded by clerks can exploit this flaw to execute arbitrary SQL commands, potentially reading sensitive data such as password hashes and modifying database contents.
OpenEMR versions prior to 8.5.0 contain an SQL injection vulnerability in the ippf_statistics.php report interface. Authenticated users with report access can manipulate the form_facility parameter to inject SQL code, potentially reading sensitive database information. The vulnerability allows attackers to close string literals in the facility_id WHERE clause and use boolean or time-based payloads. The CVSS score is 6.5, indicating a medium severity impact with high confidentiality impact but no integrity or availability impact.
OpenEMR versions prior to 8.5.0 have a missing authorization vulnerability in the portal/import_template.php component. Several portal document template modes lack proper admin/forms ACL and CSRF protections. Authenticated staff users can exploit this to delete all template profile assignments, push templates to patients, change categories, and read template bodies without proper authorization.
OpenEMR versions prior to 8.5.0 contain a path traversal vulnerability in the era_payments.php and sl_eob_search.php scripts. This flaw allows authenticated billing users to write files outside the intended ERA directory by embedding traversal sequences in the GS04 element of uploaded X12 835 files. Successful exploitation can overwrite .edi or .835 files anywhere writable by the web server, potentially leading to integrity and availability impacts.
OpenEMR versions prior to 8.5.0 have a stored cross-site scripting (XSS) vulnerability in the printed_fee_sheet.php component. Authenticated portal patients can inject malicious scripts via unescaped appointment comments, which execute in staff sessions when viewing the patient's fee sheet. This vulnerability allows limited impact on confidentiality and integrity but does not affect availability.
OpenEMR versions prior to 8.5.0 have a missing authorization vulnerability in the print_referral.php and trend_form.php scripts. This flaw allows low-privileged Front Office users to access patient protected health information (PHI) without the required patients:med permission. Attackers can exploit this by sending requests with arbitrary patient_id values to retrieve sensitive patient demographics, insurance information, and vitals history, potentially enumerating patient IDs to increase data disclosure.
OpenEMR versions prior to 8.5.0 have a missing authorization vulnerability in the ccdaservice/ccda_gateway.php component. This flaw allows any authenticated low-privilege staff user to access other patients' C-CDA documents by exploiting the view or dl actions with sequential patient IDs and their own CSRF token. Sensitive patient information such as medications, problems, allergies, and immunizations can be enumerated and exfiltrated by attackers.
OpenEMR versions prior to 8.5.0 have a stored cross-site scripting (XSS) vulnerability in the Eye Exam (eye_mag) module. This flaw allows administrators to inject malicious JavaScript through unencoded Eye_defaults list option titles. When an authenticated user clicks Defaults, the injected script executes in their session due to improper encoding in the eye_base.php file.
OpenEMR versions prior to 8.5.0 have a server-side request forgery (SSRF) vulnerability in the PatientPortalPDFDocumentCreator::createPdfObject() function. Authenticated patients can exploit this flaw by submitting crafted content parameters to portal/lib/doc_lib.php, causing the server to issue HTTP GET requests. This can be used to probe internal network ports and cloud metadata endpoints.
OpenEMR versions prior to 8.5.0 have a missing authorization vulnerability that permits any authenticated user to create patient records and enumerate existing patients. This occurs due to omitted aclCheckCore() authorization checks in certain PHP scripts. Exploitation allows attackers to create patient records containing insurance Protected Health Information (PHI) and to retrieve sensitive patient data such as names, Social Security Numbers (SSNs), and dates of birth (DOBs).
OpenEMR versions prior to 8.5.0 contain a persistent SQL injection vulnerability in the SLEOB::slInvoiceNumber() function. This flaw arises because the CLP01 claim control number from uploaded X12 835 ERA files is concatenated into a SQL query without proper escaping. Attackers with billing write access can exploit this by uploading a crafted .edi file via sl_eob_search.php, which is stored on the server and triggers a time-based SQL injection payload when reprocessed through sl_eob_process.php. The vulnerability allows extraction of patient health information.
OpenEMR versions prior to 8.5.0 have a missing authorization vulnerability in the library/ajax/user_settings.php component. This flaw allows any authenticated user to persist arbitrary global configuration overrides by sending specially crafted POST requests. Attackers can redirect external service hosts such as CouchDB, eRx, phiMail, or SMTP to attacker-controlled servers, potentially leading to exfiltration of system credentials and patient protected health information (PHI).
OpenEMR versions prior to 8.5.0 have a missing authorization vulnerability in the authorizations_full.php component. This flaw allows any authenticated staff user to authorize access to arbitrary patients' clinical records without proper provider review. Exploitation involves sending a specially crafted mode=authorize request with an attacker-chosen patient ID and a valid CSRF token, which sets authorized=1 on billing, forms, pnotes, and transactions records.
OpenEMR versions prior to 8.5.0 have a missing authorization vulnerability in the diagnosis_full.php component. Authenticated users can exploit this flaw to delete or clear billing records by specifying the billing ID and using delete or clear modes. This allows attackers to deactivate charges belonging to other patients, leading to corruption of financial records.