# CVE-2025-14301: Integration Opvius AI for WooCommerce <= 1.3.0 - Unauthenticated Arbitrary File Deletion/Read via Path Traversal

> Unauthenticated attackers can delete or read arbitrary server files via path traversal in the Integration Opvius AI for WooCommerce plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 14 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2vm4-jjww-7x6m

## What is CVE-2025-14301?

CVE-2025-14301 is a critical path traversal vulnerability in woosaai Integration Opvius AI for WooCommerce, published on 14 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Integration Opvius AI for WooCommerce plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.3.0. This is due to the `process_table_bulk_actions()` function processing user-supplied file paths without authentication checks, nonce verification, or path validation. This makes it possible for unauthenticated attackers to delete or download arbitrary files on the server via the `wsaw-log[]` POST parameter, which can be leveraged to delete critical files like `wp-config.php` or read sensitive configuration files.

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

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


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

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

## Is CVE-2025-14301 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14301 is a critical path traversal vulnerability in woosaai Integration Opvius AI for WooCommerce, published on 14 Jan 2026. 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-14301 in the wild and no public exploit code.

Affected product: woosaai Integration Opvius AI 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-14301/ (Markdown: https://insights.sbomify.com/CVE-2025-14301/index.md)
```

## Sources

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

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