dbcve.org
Emagicone Store Manager For WoocommerceWordPress extension · Emagicone

CVE-2025-4336

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-24
Fix available
A fix is available. Upgrade to after 1.2.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The eMagicOne Store Manager for WooCommerce plugin for WordPress lacks file type validation in its set_file() function, allowing unauthenticated attackers to upload arbitrary files when the default password (1:1) remains unchanged or when credentials are obtained. This enables remote code execution on the affected server.

MitigationImmediately change the default password from 1:1 to a strong, unique credential, and update the plugin to version 1.2.6 or later once released. If exploitation is suspected, conduct a full compromise assessment and remove any uploaded malicious files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Emagicone Store Manager For WoocommerceWordPress extension
Affected:<= 1.2.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the plugin is installed
    Check WordPress plugin directory for 'store-manager-for-woocommerce' folder, or query the WordPress plugins API/database for 'emagicone' or 'store-manager-for-woocommerce'
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    Read the main plugin PHP file header for the Version field, typically at wp-content/plugins/store-manager-for-woocommerce/includes/store_manager_woocommerce.php or check WordPress admin plugin list
    Affected if Version is 1.2.5 or lower
  3. Verify if default credentials are in use
    Check the plugin configuration database table (typically wp_store_manager_settings or similar) for the password field, or examine the plugin settings panel in WordPress admin for the Store Manager password setting
    Affected if Password is still set to the default value 1:1 or has not been changed from the default
  4. Audit uploaded files in the plugin directory
    Inspect the wp-content/uploads/store-manager/ directory (or similar path used by the plugin) for any unexpected PHP files, scripts, or executables that were not intentionally uploaded by administrators
    Affected if Unexpected or malicious files are present in upload directories associated with the plugin

A user is affected if the plugin version is 1.2.5 or lower AND the default password (1:1) remains unchanged, allowing unauthenticated arbitrary file upload leading to potential remote code execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.2.5
Interim mitigation

Immediately change the default password from 1:1 to a strong, unique credential, and update the plugin to version 1.2.6 or later once released. If exploitation is suspected, conduct a full compromise assessment and remove any uploaded malicious files.

Recommended fix High confidence

Version 1.2.6 or later (upgrade from 1.2.5 to latest available version)

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate 'eMagicOne Store Manager for WooCommerce' in the plugin list
  3. 3. Check the current installed version (should be 1.2.5 or lower)
  4. 4. If an update is available, click 'Update Now' to install the patched version
  5. 5. If no update appears, manually download the latest version from the WordPress Plugin Repository at wordpress.org/plugins/store-manager-for-woocommerce/
  6. 6. Deactivate and delete the current plugin, then upload and install the new version
  7. 7. After updating, ensure the default password has been changed from the default '1:1' value to a strong, unique password
  8. 8. Verify the plugin is functioning correctly by accessing Store Manager

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Emagicone Store Manager For Woocommerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4336 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data