CVE-2025-12040
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 · uneditedThe Wishlist for WooCommerce plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.1.3 via several functions in class-th-wishlist-frontend.php due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to modify other user's wishlists
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 Wishlist for WooCommerce plugin fails to validate user-controlled keys in functions within class-th-wishlist-frontend.php, allowing unauthenticated attackers to perform Insecure Direct Object Reference (IDOR) attacks and modify arbitrary users' wishlists.
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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 Wishlist for WooCommerce plugin is installedNavigate to WordPress admin > Plugins, or run 'wp plugin list' via WP-CLI, and locate 'Wishlist for WooCommerce' in the list of active pluginsAffected if The plugin is installed and active
-
Identify installed plugin versionIn WordPress admin, click on the plugin to view details and read the version number from the plugin header, or inspect the main plugin file (typically th-wishlist.php or similar in wp-content/plugins/th-wishlist-for-woocommerce/)Affected if The version cannot be determined or is lower than the patched version
-
Verify presence of vulnerable fileCheck if the file class-th-wishlist-frontend.php exists in the plugin directory at wp-content/plugins/th-wishlist-for-woocommerce/includes/class-th-wishlist-frontend.phpAffected if The file exists in the expected location
-
Confirm WooCommerce is activeCheck WooCommerce status in WordPress admin > Plugins, or run 'wp plugin status woocommerce' via WP-CLIAffected if WooCommerce is active (required for the plugin to function)
-
Inspect vulnerable functions for missing validationExamine the source code of class-th-wishlist-frontend.php and look for functions that handle user-controlled keys (request parameters) without proper authorization or ownership verification checks before performing wishlist operationsAffected if Code review reveals functions accepting user keys without validate_ownership or similar authorization checks
A user is affected if the Wishlist for WooCommerce plugin is installed with an unpatched version that lacks proper key validation in class-th-wishlist-frontend.php, allowing unauthenticated IDOR attacks on wishlist data.
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 a patched version that implements proper validation of user-controlled input and authorization checks before allowing wishlist operations, or implement input validation and ownership verification in all affected functions.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12040 — 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-12040 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