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

CVE-2025-11518

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-11
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 WPC Smart Wishlist for WooCommerce plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.0.3 via several wishlist AJAX functions due to missing validation on a user controlled key that is exposed when wishlists are shared. This makes it possible for unauthenticated attackers to empty and add to other user's wishlists, if they have access to the key.

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 WPC Smart Wishlist for WooCommerce plugin has an IDOR vulnerability in multiple wishlist AJAX functions. Due to missing validation on a user-controlled key that gets exposed when wishlists are shared, unauthenticated attackers can empty and add items to other users' wishlists if they obtain the shared key.

MitigationUpdate the plugin to version 5.0.4 or later which contains the fix. Additionally, implement proper authorization validation on all wishlist AJAX functions to ensure users can only modify their own 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
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 WPC Smart Wishlist plugin is installed
    Check your WordPress plugins directory or admin panel for 'WPC Smart Wishlist for WooCommerce' and note the installed version number
    Affected if Plugin is installed and version is below 5.0.4
  2. Confirm the wishlist sharing feature is enabled
    Navigate to plugin settings in WooCommerce > Wishlist > Settings and look for share/list options. Check if 'share' or 'public wishlist' functionality is turned on
    Affected if Wishlist sharing is enabled and the plugin version is below 5.0.4
  3. Inspect AJAX endpoint accessibility
    Examine the wp-admin/admin-ajax.php endpoints used by the plugin, specifically those handling wishlist_add, wishlist_remove, and wishlist_empty actions. Verify if unauthenticated requests can trigger these without ownership validation
    Affected if AJAX functions accept a shared key parameter without verifying the current user owns that wishlist
  4. Review shared wishlist key exposure
    Create a test shared wishlist and inspect the generated URL. Check if the share key is passed as a readable parameter (such as?share_key= or similar) that could be intercepted and reused
    Affected if The shared wishlist key is exposed in URLs and can be replayed to modify wishlists belonging to other users

Your environment is affected if WPC Smart Wishlist for WooCommerce is installed with version below 5.0.4 and the wishlist sharing feature is enabled, allowing unauthorized manipulation of other users' wishlists via exposed share keys.

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 the plugin to version 5.0.4 or later which contains the fix. Additionally, implement proper authorization validation on all wishlist AJAX functions to ensure users can only modify their own wishlists.

Recommended fix Moderate confidence

Latest version of WPC Smart Wishlist for WooCommerce (version 5.0.4 or higher)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'WPC Smart Wishlist for WooCommerce' in the plugin list
  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 via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the wishlist functionality works correctly by testing adding and removing items from a wishlist

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

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