dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-12427

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The YITH WooCommerce Wishlist plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.10.0 via the REST API endpoint and AJAX handler due to missing validation on user-controlled keys. This makes it possible for unauthenticated attackers to discover any user's wishlist token ID, and subsequently rename the victim's wishlist without authorization (integrity impact). This can be exploited to target multi-user stores for defacement, social engineering attacks, mass tampering, and profiling at scale.

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 confidence

The YITH WooCommerce Wishlist plugin for WordPress has an Insecure Direct Object Reference (IDOR) vulnerability in its REST API endpoint and AJAX handler. Due to missing validation on user-controlled keys, unauthenticated attackers can discover any user's wishlist token ID and subsequently rename the victim's wishlist without authorization.

MitigationUpgrade to version 4.10.1 or later, which adds proper validation on user-controlled keys in the REST API and AJAX endpoints to prevent unauthorized wishlist token enumeration and modification.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify YITH WooCommerce Wishlist plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or run `wp plugin list --status=active --format=csv` via WP-CLI to list active plugins
    Affected if YITH WooCommerce Wishlist does not appear in the active plugin list, then the site is not affected by this vulnerability in this specific plugin context
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate YITH WooCommerce Wishlist to view the version number; alternatively, inspect the main plugin file (yith-woocommerce-wishlist.php) in wp-content/plugins/yith-woocommerce-wishlist/
    Affected if The installed version is any version prior to 4.10.1 (e.g., 4.9.0, 4.8.0, older) indicating the vulnerable version is in use
  3. Confirm REST API endpoint exposure
    Send a GET request to the YITH wishlist REST API endpoint (typically /wp-json/yith-wcwl/v1/wishlist or similar) without authentication using curl: `curl -s https://yourdomain.com/wp-json/yith-wcwl/v1/wishlist`
    Affected if The endpoint responds with wishlist data or accepts requests without authentication, combined with a version below 4.10.1, indicating the vulnerability is present
  4. Test wishlist token enumeration
    Use an HTTP tool to send a request that attempts to access or modify a wishlist by manipulating the wishlist token ID parameter (such as yith_wcwl_token) in the AJAX endpoint /wp-admin/admin-ajax.php?action=yith_wcwl_add_to_wishlist
    Affected if The request succeeds or reveals information about a wishlist without owning or being authorized to access that specific token, confirming the IDOR vulnerability exists

If the YITH WooCommerce Wishlist plugin is active and the installed version is below 4.10.1, the environment is affected by this IDOR vulnerability allowing unauthorized wishlist access and modification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 4.10.1 or later, which adds proper validation on user-controlled keys in the REST API and AJAX endpoints to prevent unauthorized wishlist token enumeration and modification.

Recommended fix Moderate confidence

Latest version higher than 4.10.0 (check WordPress plugin repository for current release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the YITH WooCommerce Wishlist plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  6. 6. After updating, verify the wishlist functionality works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12427 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12427 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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