dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-14301

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 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.

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 Integration Opvius AI for WooCommerce plugin for WordPress is vulnerable to an unauthenticated path traversal vulnerability in the process_table_bulk_actions() function. Attackers can manipulate the wsaw-log[] POST parameter to delete or download arbitrary files on the server, including critical files like wp-config.php, leading to complete site compromise.

MitigationUpdate the plugin to a version beyond 1.3.0 immediately; if no patched version is available, disable the plugin entirely and implement WAF rules to block path traversal patterns in POST requests.

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

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. Verify the Opvius AI plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder containing 'opvius' or 'opvius-ai' and confirm the plugin is active in the WordPress admin/plugins list
    Affected if The plugin is present and active in the WordPress installation
  2. Determine the installed plugin version
    Open the main plugin PHP file and locate the version in the plugin header comment (typically at the top of the file), or check the version in the WordPress plugin admin UI
    Affected if The version is 1.3.0 or lower (versions up to and including 1.3.0 are believed affected)
  3. Confirm the vulnerable function exists
    Examine the plugin source code for the process_table_bulk_actions() function and verify it processes the wsaw-log[] POST parameter without proper sanitization
    Affected if The function exists and processes the wsaw-log[] parameter without validating file paths
  4. Test unauthenticated access to the vulnerable endpoint
    Send a crafted POST request to the affected endpoint (typically wp-admin/admin-ajax.php or similar) with the wsaw-log[] parameter containing path traversal sequences (e.g., ../../wp-config.php) without authentication cookies
    Affected if The request completes without requiring authentication and the parameter allows path traversal
  5. Inspect the plugin for proper capability checks
    Review the plugin code to verify that process_table_bulk_actions() or its calling function includes current_user_can() or similar authorization checks before processing the wsaw-log[] parameter
    Affected if No authorization check exists or the check can be bypassed, allowing unauthenticated access

The environment is affected if the Opvius AI for WooCommerce plugin is installed with version 1.3.0 or lower and the process_table_bulk_actions() function processes the wsaw-log[] parameter without authentication and path validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 1.3.0 immediately; if no patched version is available, disable the plugin entirely and implement WAF rules to block path traversal patterns in POST requests.

Recommended fix Moderate confidence

Version 1.3.1 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find 'Integration Opvius AI for WooCommerce' plugin
  4. Check if an update to version 1.3.1 or higher is available
  5. If an update is available, click 'Update Now' to install the patched version
  6. If no update is available through WordPress, manually download version 1.3.1 or higher from the WordPress plugin repository and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14301 — 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-14301 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