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/14/2026, 06:04:03 UTC

Technical Analysis

CVE-2025-14301 is a critical security vulnerability classified under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory, commonly known as Path Traversal) found in the Integration Opvius AI for WooCommerce plugin for WordPress. This vulnerability affects all versions up to and including 1.3.0. The root cause is the process_table_bulk_actions() function, which processes the wsaw-log[] POST parameter containing file paths without performing any authentication checks, nonce verification, or validation of the file paths. This lack of validation allows an unauthenticated attacker to craft malicious POST requests that specify arbitrary file paths on the server. Consequently, attackers can delete or download arbitrary files, including critical WordPress configuration files like wp-config.php, which contain database credentials and other sensitive information. The vulnerability is remotely exploitable over the network without any privileges or user interaction, making it highly dangerous. The CVSS v3.1 base score of 9.8 reflects the critical nature of this flaw, with high impacts on confidentiality, integrity, and availability. Although no known exploits have been reported in the wild yet, the ease of exploitation and the severity of potential damage make this a high-priority issue. The plugin is widely used in WooCommerce environments, which are common in e-commerce websites, increasing the attack surface. The vulnerability could lead to site defacement, data theft, or complete site compromise.

Potential Impact

For European organizations, this vulnerability poses a severe risk to e-commerce platforms running WooCommerce with the affected plugin. Successful exploitation can lead to unauthorized disclosure of sensitive data, including database credentials and customer information, violating GDPR requirements for data protection and potentially resulting in significant regulatory penalties. The ability to delete critical files like wp-config.php can cause website downtime, loss of business continuity, and damage to brand reputation. Given the popularity of WooCommerce in Europe, especially among small and medium enterprises, the threat surface is substantial. Attackers could leverage this vulnerability to gain persistent access, pivot within networks, or launch further attacks. The lack of authentication and user interaction requirements means that attackers can exploit this remotely and anonymously, increasing the likelihood of automated attacks and widespread exploitation if not promptly mitigated.

Mitigation Recommendations

Immediate mitigation steps include 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 web application firewall (WAF) rules to detect and block POST requests containing suspicious wsaw-log[] parameters or attempts at path traversal patterns (e.g., ../ sequences). Restricting access to the WordPress admin and plugin endpoints via IP whitelisting or VPN can reduce exposure. Regular backups of critical files such as wp-config.php should be maintained to enable rapid recovery in case of deletion. Additionally, monitoring server logs for unusual file access or deletion attempts can provide early detection. Security teams should audit their WordPress installations for the presence of this plugin and remove or disable it if not essential. Employing principle of least privilege on file system permissions can limit the damage if exploitation occurs. Finally, educating developers and administrators about secure coding practices, including proper input validation and authentication checks, can prevent similar vulnerabilities.

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/14/2026, 6:04:03 AM

Last updated: 1/14/2026, 5:02:45 PM

Views: 9

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