Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-4336: CWE-434 Unrestricted Upload of File with Dangerous Type in emagicone eMagicOne Store Manager for WooCommerce

0
High
VulnerabilityCVE-2025-4336cvecve-2025-4336cwe-434
Published: Sat May 24 2025 (05/24/2025, 03:37:32 UTC)
Source: CVE
Vendor/Project: emagicone
Product: eMagicOne Store Manager for WooCommerce

Description

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 14:26:22 UTC

Technical Analysis

CVE-2025-4336 is a vulnerability classified under CWE-434 (Unrestricted Upload of File with Dangerous Type) affecting the eMagicOne Store Manager for WooCommerce plugin for WordPress. The root cause is the absence of proper file type validation in the set_file() function across all versions up to and including 1.2.5. This allows unauthenticated attackers to upload arbitrary files to the server hosting the affected WordPress site. The vulnerability becomes exploitable primarily when the default credentials (username:password as 1:1) remain unchanged or if the attacker has obtained valid credentials through other means. Uploaded files could include malicious scripts that enable remote code execution (RCE), potentially allowing full system compromise. The CVSS 3.1 score of 8.1 indicates a high-severity issue with network attack vector, high complexity, no privileges required, no user interaction, and high impact on confidentiality, integrity, and availability. Despite the severity, no public exploits have been observed yet. The vulnerability affects a widely used e-commerce plugin integrated with WooCommerce, which is a popular WordPress e-commerce platform, thus posing a significant risk to online stores using this software. The lack of patch links suggests a fix may not yet be publicly available, emphasizing the need for immediate mitigation steps.

Potential Impact

If exploited, this vulnerability can lead to unauthorized file uploads, enabling attackers to execute arbitrary code on the affected server. This can result in full system compromise, data theft, defacement, or use of the server as a pivot point for further attacks. The impact extends to loss of customer trust, financial losses due to downtime or fraud, and potential regulatory penalties if sensitive data is exposed. Since WooCommerce powers many online stores globally, the threat affects e-commerce availability and integrity, potentially disrupting business operations. The requirement for default credentials or credential compromise limits the attack surface but does not eliminate risk, especially in environments with weak password policies or credential reuse. The vulnerability's network accessibility and lack of user interaction make it a potent threat if defenses are not strengthened.

Mitigation Recommendations

1. Immediately change any default credentials (username:password 1:1) associated with the eMagicOne Store Manager for WooCommerce plugin to strong, unique passwords. 2. Restrict access to the plugin’s management interfaces using IP whitelisting or VPNs to limit exposure. 3. Implement web application firewall (WAF) rules to detect and block suspicious file upload attempts, especially those targeting the set_file() function or upload endpoints. 4. Monitor server logs for unusual file upload activity or access patterns indicative of exploitation attempts. 5. Disable or remove the plugin if it is not essential to reduce the attack surface until a patch is available. 6. Regularly audit user accounts and credentials to detect and revoke unauthorized access. 7. Employ file integrity monitoring to detect unauthorized changes or uploads. 8. Stay updated with vendor advisories and apply patches promptly once released. 9. Consider isolating the WordPress environment in containers or sandboxes to limit the impact of potential compromise. 10. Educate administrators on the risks of default credentials and enforce strong password policies.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-05-05T15:40:59.839Z
Cisa Enriched
false
Cvss Version
3.1
State
PUBLISHED

Threat ID: 683142850acd01a249277dbe

Added to database: 5/24/2025, 3:52:37 AM

Last enriched: 2/27/2026, 2:26:22 PM

Last updated: 3/25/2026, 6:07:43 AM

Views: 60

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses