dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-12777

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 authorization bypass in all versions up to, and including, 4.10.0. This is due to the plugin not properly verifying that a user is authorized to perform actions on the REST API /wp-json/yith/wishlist/v1/lists endpoint (which uses permission_callback => '__return_true') and the AJAX delete_item handler (which only checks nonce validity without verifying object-level authorization). This makes it possible for unauthenticated attackers to disclose wishlist tokens for any user and subsequently delete wishlist items by chaining the REST API authorization bypass with the exposed delete_item nonce on shared wishlist pages and the AJAX handler's missing object-level authorization check.

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 up to 4.10.0 has an authorization bypass vulnerability. The REST API endpoint /wp-json/yith/wishlist/v1/lists uses permission_callback => '__return_true', allowing unauthenticated access to list wishlist tokens. Additionally, the AJAX delete_item handler only verifies nonce validity without checking object-level authorization, enabling attackers to delete wishlist items.

MitigationUpdate to version 4.10.1 or later which includes proper authorization checks. Until then, consider restricting access to the /wp-json/yith/ endpoint or implementing additional validation on the AJAX handler.

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. Confirm plugin installation and version
    Check the installed version of YITH WooCommerce Wishlist plugin in WordPress via Plugins admin page or by reading the plugin header in /wp-content/plugins/yith-woocommerce-wishlist/init.php or similar main plugin file
    Affected if The installed version is 4.10.0 or earlier (versions prior to 4.10.1)
  2. Verify REST API endpoint accessibility
    Send a GET request to /wp-json/yith/wishlist/v1/lists without providing any authentication credentials (no cookie, no token)
    Affected if The endpoint returns successful data (HTTP 200) rather than rejecting the request with an authentication/authorization error
  3. Check permission_callback in REST route registration
    Examine the plugin source code for the REST API route registration at /wp-content/plugins/yith-woocommerce-wishlist/includes/rest-api/ or similar directory; locate where the /yith/wishlist/v1/lists endpoint is registered and verify the permission_callback setting
    Affected if The permission_callback is set to '__return_true' or any function that returns true without verifying user identity
  4. Inspect AJAX delete_item handler authorization
    Review the plugin AJAX handler for delete_item action in the plugin files; verify whether the handler performs capability checks or object-level authorization beyond nonce verification
    Affected if The delete_item handler only validates nonce without checking if the current user owns or has permission to modify the specific wishlist item

A user is affected if YITH WooCommerce Wishlist version 4.10.0 or earlier is installed AND either the REST API endpoint is accessible without authentication or the AJAX delete_item handler lacks proper authorization checks beyond nonce validation.

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

Update to version 4.10.1 or later which includes proper authorization checks. Until then, consider restricting access to the /wp-json/yith/ endpoint or implementing additional validation on the AJAX handler.

Recommended fix Moderate confidence

4.10.1 or later

  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 upgrade to version 4.10.1 or later
  5. 5. Verify the update completed successfully by checking the plugin version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12777 — 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-12777 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