OpenEMR versions prior to 8.5.0 have a missing authorization vulnerability in the FaxSMS module's utility.php. This flaw allows users with read-only demographics privileges to create patient charts by submitting a form_create request with arbitrary identity fields. As a result, attackers can create fictitious or duplicate patient records including employer, history, and insurance data.
OpenEMR versions prior to 8.5.0 contain a vulnerability where authenticated users with patient or medical access can cause uncontrolled resource consumption. This is achieved by sending print_labels requests with large count parameters to labs_ajax.php, triggering excessive mPDF page and barcode generation. This can exhaust PHP workers and render the OpenEMR service unavailable.
OpenEMR versions before 8.5.0 contain a vulnerability where authenticated users can submit crafted HTML content via the doc_lib.php content parameter. This content is passed to mPDF, which processes local files and nested SVG resources, allowing attackers to read arbitrary server files including sensitive credentials and OAuth keys.
OpenEMR versions prior to 8.5.0 contain a stored cross-site scripting (XSS) vulnerability in the interface/billing/sl_eob_invoice.php component. The vulnerability arises because billing codes are escaped for HTML attributes but not for JavaScript strings within an inline onkeyup handler. This allows clinicians with encounter coding access to save crafted billing codes via diagnosis.php that execute malicious scripts when a Back Office user enters a payment. Exploitation could expose patient and financial data or allow actions to be performed as the Back Office user.
OpenEMR versions prior to 8.5.0 have an access control vulnerability in the get_claim_file.php script. When the location parameter is set to 'tmp', the script serves any file from the shared temporary directory without verifying that the file belongs to the requesting user. This allows users with certain write permissions (acct/eob or acct/bill) to download sensitive patient clinical documents, specifically the most recently validated patient's complete C-CDA clinical document.
OpenEMR versions prior to 8.5.0 have an improper authorization vulnerability in the patient_tracker_status.php component. This flaw allows low-privilege authenticated users to modify other patients' tracker entries by supplying arbitrary tracker_id values. Exploitation requires a valid CSRF token and enables attackers to alter patient-flow status, room assignments, and linked calendar appointment states.
Vvveb versions before 1.0.9.0 have a vulnerability in system/traits/media.php where a denylist bypass allows authenticated administrators to upload .phar PHP files. This misconfiguration enables attackers to upload a GIF magic-byte polyglot webshell, bypassing binary inspection and allowing execution of arbitrary OS commands as the web-server user.
Vvveb versions prior to 1.0.9.0 have an authentication bypass vulnerability in the generateCookie() function located in system/user/user.php. The vulnerability arises from the use of loose comparison to validate MD5 cookie hashes, allowing unauthenticated attackers to brute-force cookie values. When the server's MD5 computation results in a 0e magic hash, attackers can forge persistent cookies and potentially take over user accounts.
Vvveb versions up to 1.0.8.6 have a file upload vulnerability in the theme installer validFile() function. The function improperly uses strpos() for path validation instead of strict matching, allowing attackers with admin credentials to upload a ZIP archive containing a PHP file with a path including /theme.php. This can lead to remote code execution on nginx servers.
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.
Vvveb versions up to 1.0.8.6 contain an incomplete fix for CVE-2026-41934, allowing authenticated users with editor or site_admin roles to bypass save restrictions and write server-side templates. This enables attackers to upload or rename .tpl files and inject PHP code into templates, potentially leading to full compromise.
The ELEX WordPress HelpDesk & Customer Ticketing System plugin is vulnerable to PHP Object Injection in all versions up to and including 3.3.9. The vulnerability arises from missing server-side authentication and lack of a class allowlist during deserialization of the 'form' parameter, specifically the attacker-controlled ticket_label field. An attacker can harvest a publicly emitted nonce from any page with the [wsdesk_support] shortcode via an unauthenticated GET request, then perform an unauthenticated POST request to execute code on the server. This vulnerability has a critical severity with a CVSS score of 9.8.
The Chatterbug Forms WordPress plugin up to version 1.0.2 contains an arbitrary file upload vulnerability due to missing server-side file extension validation. This flaw allows unauthenticated attackers to upload potentially executable files, such as PHP scripts, enabling remote code execution. The vulnerability arises because the allowed file type check defaults to the uploaded file's extension when no restriction is configured. Additionally, the submission nonce used for access control is publicly accessible, providing no effective protection.
The Drag and Drop File Upload for Elementor Forms WordPress plugin up to version 1.6.2 contains a vulnerability that allows unauthenticated attackers to delete arbitrary files on the server. This occurs due to insufficient file path validation in the remove_files function, triggered when the "yeepdf_not_save" privacy option is enabled. Exploiting this flaw can lead to remote code execution if critical files like wp-config.php are deleted.
The NextGEN Gallery plugin for WordPress, versions up to and including 4.5.5, contains a vulnerability that allows authenticated users with custom-level access or higher to delete arbitrary files on the server. This is due to insufficient file path validation in the handle_job function. The ability to delete critical files such as wp-config.php can lead to remote code execution. By default, the 'NextGEN Manage gallery' capability required to exploit this vulnerability is granted to Administrators but can be delegated to lower-privileged roles via the plugin's Roles screen.
The Widget Options plugin for WordPress, up to and including version 4.2.6.1, contains a code injection vulnerability via the post_content parameter. This flaw arises from inconsistent parsing between save-time and render-time functions, allowing authenticated users with Author-level access or higher to inject PHP code that executes on every front-end page view. Contributors can also exploit this if their posts are published by an administrator or editor. The injected code can exfiltrate sensitive WordPress configuration data and escalate to unrestricted code execution if certain plugin filters are extended.
OpenEMR before 8.3.0 contains an unsanitized deserialization vulnerability that allows authenticated attackers to control patient-matching criteria by supplying a crafted serialized key parameter. Attackers can send serialized arrays to interface/orders/patient_match_dialog.php to enumerate patients or force matches that associate lab orders with the wrong patient.
Vvveb through 1.0.8.6 contains a cross-site request forgery vulnerability that allows attackers to perform admin state-changing actions because checkCsrf() in admin/controller/base.php only validates tokens for POST requests. Attackers can lure a logged-in admin into loading a forged cross-site GET request to delete admin/user accounts, sites, orders, and menus or change comment status.
Vvveb through 1.0.8.6 contains a remote code execution vulnerability allowing restricted site_admin roles to inject PHP by saving .sql files through the admin code editor. Attackers can bypass extension and content deny-lists with an @IF macro payload that compiles into executable PHP when the model loads, running OS commands as the web user.