# CVE-2025-32631: WordPress Oxygen MyData for WooCommerce plugin <= 1.0.64 - Arbitrary File Deletion vulnerability

> An attacker can delete arbitrary files on the server via path traversal in the Oxygen MyData for WooCommerce plugin.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-x2pr-m2jg-4p93

## What is CVE-2025-32631?

CVE-2025-32631 is a high-severity path traversal vulnerability in oxygensuite Oxygen MyData for WooCommerce, published on 11 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in oxygensuite Oxygen MyData for WooCommerce oxygen-mydata allows Path Traversal.This issue affects Oxygen MyData for WooCommerce: from n/a through <= 1.0.64.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-32631?


## How do I fix CVE-2025-32631?

No fix has been published for CVE-2025-32631 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-32631 being exploited?

There is no known exploitation of CVE-2025-32631 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32631 and fix it if it is affected.

What it is: CVE-2025-32631 is a high-severity path traversal vulnerability in oxygensuite Oxygen MyData for WooCommerce, published on 11 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32631 in the wild and no public exploit code.

Affected product: oxygensuite Oxygen MyData for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32631/ (Markdown: https://insights.sbomify.com/CVE-2025-32631/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32631
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32631
- OSV: https://osv.dev/vulnerability/CVE-2025-32631

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32631/
Summaries are generated and may contain mistakes; the official description above is the record.