CVE-2025-47687
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 Upload a Web Shell to a Web Server.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 confidenceThe StoreKeeper for WooCommerce plugin has an unrestricted file upload vulnerability allowing attackers to upload arbitrary file types including PHP scripts (web shells) directly to the web server. This enables complete remote code execution and full system compromise.
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.
-
Verify StoreKeeper for WooCommerce is installedLog in to WordPress admin, go to Plugins > Installed Plugins, and search for 'StoreKeeper for WooCommerce' or check the plugin directory /wp-content/plugins/ for storekeeper-woocommerce folderAffected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin, click on the StoreKeeper for WooCommerce plugin to view its details, or inspect the main plugin file (usually storekeeper-woocommerce.php) to find the Version headerAffected if The installed version is lower than the patched version published for this CVE
-
Inspect upload directories for unexpected file typesNavigate to /wp-content/uploads/ (and any custom upload directories configured in WooCommerce) and list files with extensions such as .php, .phtml, .php5, .phar, or .exe that were added recentlyAffected if PHP files or other executable scripts exist in upload directories, indicating possible exploitation
-
Review web server access logs for file upload activityExamine web server logs (Apache error.log, access.log or Nginx access.log, error.log) for POST requests to /wp-admin/admin-ajax.php or the StoreKeeper endpoint that include filenames with .php extensionsAffected if Logs show uploads of .php files or other suspicious file types to upload directories
A user is affected if StoreKeeper for WooCommerce is installed and the version is older than the patched release, or if unauthorized PHP/executable files are found 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 dataUpdate StoreKeeper for WooCommerce to the latest patched version immediately. If no patch is available, disable the plugin and implement web server-level restrictions to block PHP execution in upload directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47687 — 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-47687 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