eMagicOne Store Manager for WooCommerce Security & Risk Analysis

wordpress.org/plugins/store-manager-connector

Store Manager Connector is used to connect Store Manager to WooCommerce database in convenient and quick way.

500 active installs v1.3.2 PHP 5.4+ WP 4.1.1+ Updated Dec 9, 2025
bulk-updatechatgptexportimportwoocommerce
48
D · High Risk
CVEs total5
Unpatched1
Last CVEMay 7, 2026
Safety Verdict

Is eMagicOne Store Manager for WooCommerce Safe to Use in 2026?

High Risk

Score 48/100

eMagicOne Store Manager for WooCommerce carries significant security risk with 5 known CVEs, 1 still unpatched. Consider switching to a maintained alternative.

5 known CVEs 1 unpatched Last CVE: May 7, 2026Updated 8mo ago
Risk Assessment

The "store-manager-connector" plugin v1.3.2 exhibits a mixed security posture. On the positive side, the static analysis shows a complete lack of direct entry points like AJAX handlers, REST API routes, shortcodes, and cron events that are not protected by authorization checks. Furthermore, all SQL queries utilize prepared statements, and a high percentage of output is properly escaped. The plugin also includes nonce and capability checks. However, significant concerns arise from the presence of the `unserialize` function, which is a known vector for remote code execution if used with untrusted input. Taint analysis reveals two flows with unsanitized paths, both flagged with high severity, indicating potential vulnerabilities related to file operations or path manipulation. The plugin's vulnerability history is a major red flag, with four known CVEs, including two critical and one high severity, and a recent vulnerability discovered in May 2025. The common types of past vulnerabilities (External Control of File Name or Path, Unrestricted Upload of File with Dangerous Type) directly correlate with the concerns identified in the taint analysis. While the current version appears to have no unpatched CVEs, the historical pattern suggests a recurring susceptibility to these types of attacks. In conclusion, despite good practices in input sanitization for SQL and output escaping, the identified `unserialize` function and the high-severity unsanitized paths in taint analysis, coupled with a concerning vulnerability history, necessitate caution and thorough investigation.

Key Concerns

  • High severity unsanitized paths in taint analysis (2 flows)
  • Presence of dangerous unserialize function
  • History of 2 critical CVEs
  • History of 1 high CVE
  • History of 1 medium CVE
Vulnerabilities
5 published

eMagicOne Store Manager for WooCommerce Security Vulnerabilities

CVEs by Year

4 CVEs in 2025
2025
1 CVE in 2026 · unpatched
2026
Patched Has unpatched

Severity Breakdown

Critical
2
High
2
Medium
1

5 total CVEs

CVE-2026-42773high · 7.5Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

eMagicOne Store Manager for WooCommerce <= 1.3.2 - Unauthenticated SQL Injection

May 7, 2026Unpatched
CVE-2025-5058critical · 9.8Unrestricted Upload of File with Dangerous Type

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

May 23, 2025 Patched in 1.3.0 (166d)
CVE-2025-4602medium · 5.9External Control of File Name or Path

eMagicOne Store Manager for WooCommerce <= 1.2.5 - Unauthenticated Arbitrary File Read

May 23, 2025 Patched in 1.3.0 (166d)
CVE-2025-4603critical · 9.1External Control of File Name or Path

eMagicOne Store Manager for WooCommerce <= 1.2.5 - Unauthenticated Arbitrary File Deletion

May 23, 2025 Patched in 1.3.0 (166d)
CVE-2025-4336high · 8.1Unrestricted Upload of File with Dangerous Type

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

May 23, 2025 Patched in 1.3.0 (166d)
Version History

eMagicOne Store Manager for WooCommerce Release Timeline

Code Analysis
Analyzed Mar 16, 2026

eMagicOne Store Manager for WooCommerce Code Analysis

Dangerous Functions
1
Raw SQL Queries
0
5 prepared
Unescaped Output
14
91 escaped
Nonce Checks
2
Capability Checks
2
File Operations
27
External Requests
0
Bundled Libraries
0

Dangerous Functions Found

unserializereturn unserialize( $data );classes\class-emosmcwoocommerceoverrider.php:977

SQL Query Safety

100% prepared5 total queries

Output Escaping

87% escaped105 total outputs
Data Flows · Security
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
add_failed_attempt (classes\class-emosmconnectorcommon.php:2587)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

eMagicOne Store Manager for WooCommerce Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 8
actionadmin_menuclasses\class-emosmconnectorconnectorsettingspage.php:40
actionadmin_initclasses\class-emosmconnectorconnectorsettingspage.php:41
actionadmin_enqueue_scriptsclasses\class-emosmconnectorstart.php:34
filterquery_varsclasses\class-emosmconnectorstart.php:35
actiontemplate_redirectclasses\class-emosmconnectorstart.php:36
actionplugins_loadedclasses\class-emosmconnectorstart.php:37
filterupload_dirclasses\class-emosmcwoocommerceoverrider.php:506
actionadmin_noticessmconnector.php:192
Maintenance & Trust

eMagicOne Store Manager for WooCommerce Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.5
Last updatedDec 9, 2025
PHP min version5.4
Downloads27K

Community Trust

Rating66/100
Number of ratings10
Active installs500
Developer Profile

eMagicOne Store Manager for WooCommerce Developer Profile

eMagicOne

2 plugins · 510 total installs

61
trust score
Avg Security Score
74/100
Avg Patch Time
166 days
View full developer profile
Detection Fingerprints

How We Detect eMagicOne Store Manager for WooCommerce

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about eMagicOne Store Manager for WooCommerce