CVE-2025-48148

StoreKeeper for WooCommerce <= 14.4.4 - Unauthenticated Arbitrary File Upload

2025-07-31 00:00
theviper17y

Strategic Overview

Status
Patched in 14.4.5
Affected Version
<= 14.4.4
CVSS
9.8Critical
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2025-48148
View all StoreKeeper for WooCommerce vulnerabilities

At a glance

CVE-2025-48148 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the StoreKeeper for WooCommerce WordPress plugin, affecting versions <= 14.4.4. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 14.4.5; sites on affected versions should update now. Disclosed July 2025, reported by theviper17y.

Vulnerability Overview

The StoreKeeper for WooCommerce plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in all versions up to, and including, 14.4.4. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in StoreKeeper for WooCommerce <= 14.4.4 takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For StoreKeeper for WooCommerce the fix is 14.4.5: builds <= 14.4.4 are affected, anything from 14.4.5 onward is not.

Remediation

Update to version 14.4.5, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: StoreKeeper for WooCommerce 14.4.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C