CVE-2025-5058: eMagicOne Store Manager for WooCommerce <= 1.2.5 - Unauthenticated Arbitrary File Upload via set_image()
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.
Security readout for executives and security teams
Plain-English summary
Affected WooCommerce sites may allow attackers to place arbitrary files on the server. This could enable site takeover, data theft, malicious checkout changes, or service disruption. The highest exposure occurs when the Store Manager connector retains its default 1:1 password or its credentials have been compromised.
Executive priority
Treat exposed installations as an immediate remediation priority because successful exploitation could compromise the entire website and its data. Prioritize internet-reachable commerce sites, rotate connector credentials, restrict access, and update or disable the plugin. Investigate for compromise when default or exposed credentials were present.
Technical view
CVE-2025-5058 is a CWE-434 flaw in the plugin’s set_image() function, which lacks adequate file-type validation through version 1.2.5. A network attacker with the default connector password or acquired credentials may upload arbitrary files, potentially achieving remote code execution. CVSS 3.1 is 9.8.
Likely exposure
Exposure is limited to sites running eMagicOne Store Manager for WooCommerce through version 1.2.5 where the connector is reachable and uses default or compromised credentials. Sites without the plugin, outside the stated version range, or with inaccessible connectors are not shown as affected by this bundle.
Exploitation context
The bundle includes public technical references, but it does not establish active exploitation, and the CVE is not listed as KEV. Exploitation is described as possible when the default 1:1 password remains configured or an attacker obtains connector credentials.
Researcher notes
The narrative evidence states that all versions through 1.2.5 are affected and points to relevant source lines and a WordPress changeset. However, the structured affected entry lists version “0” with defaultStatus “unaffected,” creating a data-quality inconsistency. Confirm exact fixed-version boundaries with vendor guidance before closing remediation tickets.
Mitigation direction
Update to a vendor-confirmed fixed release; the bundle does not identify a fixed version.
Immediately replace the default 1:1 connector password with a strong, unique credential.
Restrict connector access to trusted networks or systems where operationally possible.
If updating is unavailable, disable the connector and consult current vendor guidance.
Review the server for unauthorized uploads and investigate suspicious files before restoring normal access.
Validation and detection
Inventory WordPress sites for the plugin and record every installed version.
Verify whether the default connector password remains configured or credentials may be exposed.
Confirm the connector endpoint is inaccessible from untrusted networks where restrictions are intended.
Review connector, web-server, and security logs for unexpected upload activity.
After remediation, confirm benign disallowed file types are rejected in a controlled environment.
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.
1CVSS vectors
4Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
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.