Skip to content
Web

CVE-2025-14301

9.8
Critical
EPSS 0.69%Jan 14, 2026

Unauthenticated path traversal in Opvius AI for WooCommerce enables arbitrary file delete/read via wsaw-log[].

common questions

Is CVE-2025-14301 being exploited?

Not confirmed. CVE-2025-14301 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.69% probability of exploitation in the next 30 days.

How severe is CVE-2025-14301?

CVE-2025-14301 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-14301?

Not known from our data. No patch reference has been recorded for CVE-2025-14301, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2025-14301 affect?

CVE-2025-14301 affects WordPress, Opvius AI for WooCommerce plugin, WooCommerce site. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-14301?

Update to latest version or remove vulnerable plugin.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WordPressOpvius AI for WooCommerce pluginWooCommerce site
impact

Unauthenticated attacker can delete or read arbitrary server files (e.g., wp-config.php) via wsaw-log[]; may lead to full site compromise.

action required

Patch when possible

affected versions
woosaai Integration Opvius AI for WooCommerce
  • affected<= 1.3.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free