CVE-2025-5058

eMagicOne Store Manager for WooCommerce <= 1.2.5 - Unauthenticated Arbitrary File Upload via set_image()

2025-05-23 14:33
Ryan Kozak

Strategic Overview

Status
Patched in 1.3.0
Affected Version
<= 1.2.5
CVSS
9.8Critical
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2025-5058
View all eMagicOne Store Manager for WooCommerce vulnerabilities

At a glance

CVE-2025-5058 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the eMagicOne Store Manager for WooCommerce WordPress plugin, affecting versions <= 1.2.5. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.3.0; sites on affected versions should update now. Disclosed May 2025, reported by Ryan Kozak.

Vulnerability Overview

The eMagicOne Store Manager for WooCommerce plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the set_image() 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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

eMagicOne Store Manager for WooCommerce <= 1.2.5 carries this weakness at set_image(), and reaching it takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For eMagicOne Store Manager for WooCommerce the fix is 1.3.0: builds <= 1.2.5 are affected, anything from 1.3.0 onward is not.

Remediation

Update to version 1.3.0, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: eMagicOne Store Manager for WooCommerce 1.3.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C