Zipline versions through 4.4.0 have a path traversal vulnerability in the PATCH /api/user/files/:id rename endpoint. Authenticated users can exploit this flaw by supplying crafted file names that bypass database uniqueness checks but are normalized by the system, allowing overwriting of existing uploaded files.
Zipline versions before 4.6.2 have a missing authorization vulnerability in the POST /api/user/folders endpoint. Authenticated users can exploit this flaw to reparent files belonging to other users by supplying their file IDs. Attackers can gather these file IDs from public folders, create a folder containing them, and thereby disclose the victims' file URLs while removing those files from the victims' folder views.
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 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 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 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 an SQL injection vulnerability in the Syndromic Surveillance report. This flaw arises because the form_icd_codes[] POST parameter is concatenated into an unquoted numeric IN() clause without proper integer validation. Authenticated users can exploit this by submitting quote-free payloads that bypass escaping functions, enabling blind or UNION-based SQL injection attacks to exfiltrate patient health information.
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 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 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.
OpenEMR versions prior to 8.5.0 have a missing authorization vulnerability in the trusted-messages-ajax.php component. This flaw allows any authenticated core user to send Direct messages without requiring the patients/notes permission. Attackers with zero-ACL accounts can exploit this to send messages impersonating the clinic using the clinic's phiMail credentials, enabling fraudulent clinical communications.
OpenEMR versions prior to 8.5.0 have an improper authorization vulnerability in the interface/orders/list_reports.php component. This flaw allows users with read-only access to transmit laboratory orders by bypassing write permission checks. Authenticated attackers can exploit this by submitting arbitrary procedure order IDs to send HL7 orders containing sensitive patient information such as SSNs, insurance details, and diagnoses to laboratories, and mark these orders as transmitted.
Coder versions 2.26.0 before 2.29.24, 2.30.0 before 2.34.16, 2.35.0 before 2.36.11, 2.37.0 before 2.37.8, and 2.38.0 before 2.38.4 contain an improper authorization vulnerability. This flaw allows authenticated users with workspace read access but without SSH permission to obtain the workspace agent token. Users with roles such as Template Admin or Organization Admin can exploit this to access the owner's private Git SSH key and Git provider OAuth tokens, enabling session impersonation.
vLLM versions from 0.30.0 up to but not including 0.31.0 contain a resource exhaustion vulnerability in the OpenCVDynamicOpenPanguVideoBackend component. This vulnerability arises because the num_frames parameter, controlled by the request, lacks an effective upper limit. Unauthenticated attackers can exploit this by sending requests to /v1/chat/completions or /tokenize endpoints with a large num_frames value, causing excessive CPU usage and memory allocation that can lead to the API server being terminated by the operating system's out-of-memory killer.
vLLM versions from 0.24.0 up to but not including 0.31.0 contain a resource exhaustion vulnerability in the MiniMax M3 VL video processor. The vulnerability arises because the processor accepts a request-level min_pixels parameter without proper validation against range or max_pixels. Since the video-wide pixel budget enforcement depends on max_long_side_pixel, which defaults to None, API clients can exploit this by supplying a large min_pixels value. This causes excessive CPU and host memory consumption, potentially disrupting worker processes or the overall service.
n8n versions prior to 2.46.1 have an arbitrary file read vulnerability that allows authenticated users to read server files by providing absolute paths via the browser_upload tool. This can expose sensitive server files such as instance configuration. The vulnerability requires authenticated access and a connected remote browser session using Playwright to exploit.
An SQL injection vulnerability exists in the Vector Store (OracleDB) node of n8n versions before 2.43.5, 2.44.x before 2.44.1, and 3.x before 3.0.1. This flaw arises because the node does not validate Metadata Filter keys used in vector search queries. Attackers can exploit this by supplying crafted filter keys via untrusted workflow inputs such as webhooks, potentially allowing unauthorized reading of data accessible to the Oracle credential configured in n8n.
Vvveb versions up to 1.0.8.6 have an SQL injection vulnerability in the Admin_Auth_TokenSQL::update() function. This flaw arises because the function interpolates admin_auth_token array keys directly into an SQL INSERT column list without proper column whitelisting or escaping. Authenticated users with admin panel access can exploit this by submitting specially crafted keys containing backticks, enabling injection of SQL comments and column identifiers.
Vvveb versions up to 1.0.8.6 have an SQL injection vulnerability due to improper handling of PHP array keys in SQL statements. Authenticated back-office users who can save products may exploit this by submitting specially crafted POST data containing backticks, which can manipulate SQL queries by redirecting values into unintended columns or breaking the SQL syntax.