Arbitrary File Upload in eMagicOne Store Manager for WooCommerce
CVE-2025-4336 affects the eMagicOne Store Manager for WooCommerce plugin for WordPress. In all versions up to and including 1.2.5, the plugin's set_file() function does not properly validate uploaded file types, allowing arbitrary file upload to the server. Because an attacker can upload files not intended by the application, this can lead to execution of attacker-controlled code if the uploaded file is placed in a web-accessible or otherwise executable location. The issue is described as exploitable by unauthenticated attackers in default configurations when the default password remains set to 1:1, or by attackers who otherwise obtain valid credentials.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows an attacker to upload arbitrary files to the affected server. Depending on server configuration and file placement, this may enable remote code execution in the context of the web application, resulting in full compromise of the WordPress site, unauthorized modification of site content, deployment of webshells or other malware, theft of sensitive data, and potential persistence or follow-on lateral activity from the compromised host.
If you can’t patch tonight, do this now.
Immediately change any default credentials, especially if the plugin is still configured with the default password 1:1. Restrict access to the plugin interface to trusted administrators only, limit network exposure where possible, and monitor for unexpected file uploads or newly created executable files in upload directories. Configure the web server to prevent execution of scripts from upload locations, apply least-privilege filesystem permissions, and consider temporary removal or deactivation of the plugin until a patched release is installed.
Patch, then assume compromise.
Update the eMagicOne Store Manager for WooCommerce plugin to a version newer than 1.2.5 if a vendor fix is available. If no patched version is yet available, remove or disable the plugin until a fix is released. The underlying issue should be remediated by implementing strict server-side file type validation in set_file(), enforcing an allowlist of permitted extensions and MIME types, rejecting executable or dangerous file formats, and ensuring uploaded files cannot be executed by the web server.
1 exploit validated by Mallory's analysis.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.