CVE-2025-4336: eMagicOne Store Manager for WooCommerce <= 1.2.5 - Unauthenticated Arbitrary File Upload via set_file()
The eMagicOne Store Manager for WooCommerce plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the set_file() function in all versions up to, and including, 1.2.5. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. This is only exploitable by unauthenticated attackers in default configurations where the the default password is left as 1:1, or where the attacker gains access to the credentials.
Security readout for executives and security teams
Plain-English summary
Affected WooCommerce stores may allow an outside attacker to place arbitrary files on the server. Successful abuse could expose data, alter the store, disrupt service, or potentially enable remote code execution. Unauthenticated exploitation depends on the connector retaining its default 1:1 password; stolen connector credentials create similar exposure.
Executive priority
Treat this as a high-priority exposure check, especially for public ecommerce systems. Identify affected installations promptly, remove default credentials, and update using confirmed vendor guidance. Escalate to incident response if unexpected uploads, connector access, or server-side files are found.
Technical view
CVE-2025-4336 is a CWE-434 unrestricted file-upload flaw in the plugin’s set_file() function through version 1.2.5. Missing file-type validation permits arbitrary uploads. CVSS 3.1 scores it 8.1. Remote code execution is possible but not guaranteed, and exploitation requires the default 1:1 password or obtained credentials.
Likely exposure
Internet-accessible WordPress sites running eMagicOne Store Manager for WooCommerce 1.2.5 or earlier require review. Risk is greatest where the connector uses the default 1:1 password. The supplied version metadata is internally inconsistent, so confirm the installed plugin identity and version directly.
Exploitation context
CISA KEV status is false, and the supplied sources do not establish active exploitation. Public technical references exist, including researcher and GitHub pages, but their presence alone does not prove attacks in the wild. Exploitation is conditional on default or compromised connector credentials.
Researcher notes
The high impact reflects potential compromise of confidentiality, integrity, and availability. CVSS complexity is high because exploitation depends on usable connector credentials, although privileges are scored none. The sources identify a WordPress changeset, but the bundle does not explicitly name a fixed version or establish that code execution occurred.
Mitigation direction
Update to a vendor-confirmed fixed release after reviewing current vendor guidance.
Immediately replace the default 1:1 connector password with a strong, unique credential.
Rotate connector credentials if exposure or compromise cannot be ruled out.
Restrict connector access to trusted networks or addresses where operationally possible.
Disable and remove the plugin if it is unnecessary or cannot be safely updated.
Validation and detection
Inventory WordPress sites for the plugin and record each installed version.
Confirm whether the connector still accepts the default 1:1 password.
Review connector access logs for unexpected sources, authentication activity, and upload requests.
Inspect writable directories and web-accessible paths for unexpected or recently created files.
Verify the installed release against vendor guidance identifying the corrected version.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-434 · source CWE mapping
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.