CVE-2025-47577
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 templateinvaders TI WooCommerce Wishlist ti-woocommerce-wishlist allows Upload a Web Shell to a Web Server.This issue affects TI WooCommerce Wishlist: from n/a through <= 2.9.2.
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 TI WooCommerce Wishlist plugin before version 2.9.3 contains an unrestricted file upload vulnerability that allows authenticated attackers to upload arbitrary files, including malicious web shells, to the web server. This enables complete remote code execution on the affected WordPress/WooCommerce installation.
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.
-
Confirm TI WooCommerce Wishlist plugin is installedNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'TI WooCommerce Wishlist' in the list of active pluginsAffected if The plugin appears in the installed plugins list
-
Identify the installed version of the pluginIn the Plugins list, find the TI WooCommerce Wishlist entry and locate the version number displayed beneath the plugin nameAffected if The displayed version number is lower than 2.9.3 (for example, 2.9.2, 2.9.1, 2.8.x, etc.)
-
Verify the upload functionality is accessibleCheck if the wishlist plugin's file upload endpoint is reachable; typical paths include /wp-content/plugins/ti-woocommerce-wishlist/ or similar; attempt to access upload-related AJAX actions or endpoints using a browser or curlAffected if The upload functionality endpoint responds without authentication errors or returns a valid upload form/handler
-
Inspect upload directories for suspicious filesSearch the wp-content/uploads/ directory (and any subdirectories created by the wishlist plugin) for files with extensions such as .php, .phtml, .phar, or .phpt that were recently modified; use file search commands like find or inspect via FTP/file managerAffected if Unexpected PHP files or other executable scripts are found in upload directories, especially if they were created recently and contain suspicious code
A user is affected if the TI WooCommerce Wishlist plugin is installed with a version lower than 2.9.3 and the upload functionality is accessible to authenticated users.
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 to TI WooCommerce Wishlist version 2.9.3 or later which patches the unrestricted file upload vulnerability. Additionally, implement proper file type validation, store uploads outside the web root, disable script execution in upload directories, and review user access controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47577 — 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-47577 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