LiveActive security incident?Get immediate response
CVE Record

CVE-2025-4603: eMagicOne Store Manager for WooCommerce <= 1.2.5 - Unauthenticated Arbitrary File Deletion

The eMagicOne Store Manager for WooCommerce plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_file() function in all versions up to, and including, 1.2.5. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). 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.

CriticalCVSS 9.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

An attacker who can reach a vulnerable WooCommerce connector may delete server files without WordPress authentication when its default 1:1 password remains or connector credentials are stolen. Deleting configuration or application files could take the store offline and may create a path to server code execution. The impact is critical, but exposure depends on the plugin and credential condition.

Executive priority

Treat as an immediate priority wherever the affected connector is internet-reachable with default or exposed credentials. File deletion could take stores offline and may escalate to server compromise. Rapidly inventory deployments, remove credential exposure, restrict access, and follow vendor remediation guidance. Sites without the plugin are not exposed to this CVE.

Technical view

A CWE-73 path-handling weakness in delete_file() permits attacker-controlled file deletion. Network exploitation requires the connector's default 1:1 password or obtained credentials. Deleting critical WordPress files can undermine availability and integrity and may enable code execution, although the bundle does not establish that code execution always follows.

Likely exposure

Likely exposure is limited to WordPress/WooCommerce deployments running eMagicOne Store Manager for WooCommerce through 1.2.5 where the connector is reachable and retains 1:1 credentials, or credentials have been compromised. Deployments without the plugin or outside the stated affected range are not shown exposed by this bundle.

Exploitation context

KEV status is false, and the bundle provides no evidence of active exploitation. Public exploit-oriented research is referenced, so defenders should assume technical details are accessible. Exploitation remains conditional on default or compromised connector credentials.

Researcher notes

The title and narrative define affected versions through 1.2.5, but the structured affected record lists version "0" with default status unaffected. Treat this metadata inconsistency cautiously. The referenced WordPress changeset suggests remediation activity, but the bundle does not explicitly identify a fixed release.

Mitigation direction

  • Disable or remove affected releases until vendor guidance confirms a remediated version.
  • Replace the default 1:1 connector password with a strong, unique credential and rotate exposed secrets.
  • Restrict connector access to trusted administrative networks or systems where operationally possible.
  • Use verified backups to restore deleted files only after investigating possible compromise.
  • Monitor vendor and WordPress guidance because the source bundle does not name a fixed release.

Validation and detection

  • Inventory WordPress sites for eMagicOne Store Manager for WooCommerce and record installed versions.
  • Confirm whether connector credentials remain 1:1, then rotate any default or potentially exposed credentials.
  • Review server and application logs for suspicious connector requests and unauthorized file deletion activity.
  • Compare critical WordPress files against trusted backups or known-good hashes.
  • Check backup integrity and investigate unexplained missing or modified files before restoration.
Prepared
Confidence
medium
Sources
7

Public sources used

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-73: 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.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

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.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

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.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-4603 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H3.95.2Wordfence

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2025-4603Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. Source timelineWordfence

    Disclosed

  3. CVE publishedCVE Program

    The CVE record was published.

  4. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
emagiconeeMagicOne Store Manager for WooCommerce0unaffected
Weakness

CWE details

CWE-73

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-73 · source CWE mapping

External Control of File Name or Path

External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs