CVE-2025-48148
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnrestricted 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStoreKeeper for WooCommerce plugin versions up to 14.4.4 contain an unrestricted file upload vulnerability allowing attackers to upload dangerous file types (e.g., executable scripts) without proper validation, potentially enabling remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the StoreKeeper for WooCommerce plugin installationCheck the WordPress plugins directory (typically wp-content/plugins/storekeeper-woocommerce/) or use WP-CLI: wp plugin list --name='storekeeper-woocommerce'Affected if The plugin is not present in the WordPress installation
-
Identify the installed plugin versionRead the main plugin file header (e.g., storekeeper-woocommerce.php) to find the 'Version:' tag, or run: grep -i 'Version:' wp-content/plugins/storekeeper-woocommerce/*.php | head -5Affected if The version number is 14.4.4 or lower (including any 14.x.y version where y <= 4 or any 14.x.x version where x < 4)
-
Determine if file upload functionality is activeCheck if the StoreKeeper sync or import feature is enabled in WooCommerce settings under StoreKeeper > Settings, or inspect if the upload endpoint exists by checking WooCommerce REST API routes for storekeeperAffected if File upload/sync features are enabled and accessible
-
Inspect the uploads directory for suspicious filesExamine wp-content/uploads/ and subdirectories for unexpected file extensions such as .php, .phtml, .js, .sh, .asp, .exe, or other executable types that should not be presentAffected if Any script files (.php, .phtml, etc.) are found in upload directories that were not explicitly authorized
A user is affected if the StoreKeeper for WooCommerce plugin is installed at version 14.4.4 or lower and file upload functionality is enabled, particularly if untrusted executable files are present in upload directories.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict file type validation using a whitelist of allowed extensions and MIME types, perform server-side validation, store uploads outside webroot, and disable script execution in upload directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48148 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data