Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14301: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in woosaai Integration Opvius AI for WooCommerce

0
Critical
VulnerabilityCVE-2025-14301cvecve-2025-14301cwe-22
Published: Wed Jan 14 2026 (01/14/2026, 05:28:05 UTC)
Source: CVE Database V5
Vendor/Project: woosaai
Product: Integration Opvius AI for WooCommerce

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.

AI-Powered Analysis

AILast updated: 01/21/2026, 20:25:58 UTC

Technical Analysis

CVE-2025-14301 is a critical security vulnerability identified in the Integration Opvius AI for WooCommerce plugin for WordPress, affecting all versions up to and including 1.3.0. The root cause is improper limitation of pathname to a restricted directory (CWE-22), specifically in the process_table_bulk_actions() function. This function processes user-supplied file paths through the wsaw-log[] POST parameter without performing authentication checks, nonce verification, or validating the file paths. As a result, unauthenticated attackers can exploit this flaw to perform path traversal attacks, allowing them to delete or download arbitrary files on the server. Critical files such as wp-config.php, which contains database credentials and other sensitive configuration data, can be targeted. The vulnerability is remotely exploitable without any user interaction or privileges, making it highly dangerous. The CVSS v3.1 base score is 9.8, reflecting the high impact on confidentiality, integrity, and availability. Although no exploits have been observed in the wild yet, the vulnerability's nature and ease of exploitation make it a significant threat to WordPress sites using this plugin. The lack of authentication and nonce checks further exacerbates the risk, as attackers can directly send crafted POST requests to trigger the vulnerability.

Potential Impact

For European organizations, especially those operating e-commerce platforms using WooCommerce with the Integration Opvius AI plugin, this vulnerability poses a severe risk. Exploitation can lead to unauthorized disclosure of sensitive configuration files, resulting in credential theft, data breaches, and potential full site compromise. Deletion of critical files can cause denial of service, disrupting business operations and damaging reputation. Given the widespread use of WooCommerce in Europe, particularly in countries with strong e-commerce sectors like Germany, the UK, France, and the Netherlands, the impact could be substantial. Attackers could leverage this vulnerability to gain persistent access, pivot within networks, or launch further attacks. The absence of authentication requirements means that even external attackers without any prior access can exploit the flaw, increasing the attack surface. Regulatory implications under GDPR may also arise if personal data is exposed or lost due to exploitation.

Mitigation Recommendations

Immediate mitigation involves updating the Integration Opvius AI for WooCommerce plugin to a patched version once released by the vendor. Until a patch is available, organizations should implement strict web application firewall (WAF) rules to detect and block requests containing suspicious wsaw-log[] POST parameters or path traversal patterns. Restricting access to the WordPress admin and plugin endpoints via IP whitelisting or VPN can reduce exposure. Additionally, disabling or removing the vulnerable plugin if it is not essential is advisable. Monitoring server logs for unusual file access or deletion attempts related to this parameter can help detect exploitation attempts early. Employing file integrity monitoring solutions to alert on changes to critical files like wp-config.php is recommended. Finally, ensure regular backups are maintained and tested to enable rapid recovery in case of file deletion or compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-08T22:16:03.894Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69672e008330e067168f3fbf

Added to database: 1/14/2026, 5:47:44 AM

Last enriched: 1/21/2026, 8:25:58 PM

Last updated: 2/6/2026, 2:06:47 AM

Views: 53

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats