Summary
CVE-2026-8778 is a critical arbitrary file upload vulnerability in the MIPL Grouped Checkout Fields for WooCommerce WordPress plugin, developed by Mulika. The plugin fails to validate file types in its mipl_wc_upload_file function, allowing unauthenticated attackers to upload arbitrary files — including malicious PHP scripts — to affected WordPress sites. Given the CVSS score of 9.8 (Critical) and lack of any authentication requirement, successful exploitation can lead to full remote code execution and complete compromise of the underlying web server.
Technical details
- Root cause: The plugin’s
mipl_wc_upload_filefunction, used to handle file uploads submitted through custom checkout fields, does not validate the file type/extension of uploaded content before saving it to the server. - Trigger conditions: No authentication or special privileges are required; the vulnerable upload functionality is reachable by unauthenticated visitors interacting with the WooCommerce checkout process.
- Attack vector: Network-based (remote), low attack complexity, no user interaction required.
- Impact: An attacker can upload a web shell or other executable script disguised as a checkout attachment, then access it directly to execute arbitrary PHP code on the server — resulting in full compromise of confidentiality, integrity, and availability of the affected site.
Affected software
- MIPL Grouped Checkout Fields for WooCommerce – Customize & Organize Checkout Fields (WordPress plugin, vendor: Mulika)
- Versions: all versions up to and including 1.2.2
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Update the MIPL Grouped Checkout Fields for WooCommerce plugin to a patched version above 1.2.2 as soon as the vendor releases a fix. At the time of disclosure, check the WordPress.org plugin page for the latest release and changelog confirming the file-upload/type-validation fix.
- If no patch is available: Disable or uninstall the plugin until a fixed version is released. As a temporary compensating control, restrict or block public access to the plugin’s upload-handling endpoint at the web server or WAF layer, and audit the uploads directory for unexpected executable files (e.g.,
.php,.phtml). - General hardening: Ensure the WordPress uploads directory disallows execution of PHP files (via web server configuration), and monitor for newly created files in upload paths as an indicator of exploitation attempts.

