# CVE-2025-48148: WordPress StoreKeeper for WooCommerce Plugin <= 14.4.4 - Arbitrary File Upload Vulnerability

> Attackers can upload malicious files to the StoreKeeper for WooCommerce plugin, potentially leading to remote code execution on the WordPress site.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-999h-7g64-qf64

## What is CVE-2025-48148?

CVE-2025-48148 is a critical vulnerability in StoreKeeper for WooCommerce, published on 20 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unrestricted Upload of File with Dangerous Type vulnerability in StoreKeeper B.V. StoreKeeper for WooCommerce storekeeper-for-woocommerce allows Using Malicious Files.This issue affects StoreKeeper for WooCommerce: from n/a through <= 14.4.4.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2025-48148?


## How do I fix CVE-2025-48148?

No fix has been published for CVE-2025-48148 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-48148 being exploited?

There is no known exploitation of CVE-2025-48148 in the wild and no public exploit code.

Public exploit code:

- StoreKeeper for WooCommerce <= 14.4.4 - Unauthenticated Arbitrary File Upload (github_poc): https://github.com/Nxploited/CVE-2025-48148

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48148 and fix it if it is affected.

What it is: CVE-2025-48148 is a critical vulnerability in StoreKeeper for WooCommerce, published on 20 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48148 in the wild and no public exploit code.

Affected product: StoreKeeper for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-48148/ (Markdown: https://insights.sbomify.com/CVE-2025-48148/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48148
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48148
- OSV: https://osv.dev/vulnerability/CVE-2025-48148

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-48148/
Summaries are generated and may contain mistakes; the official description above is the record.