dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13440

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-12
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 Premmerce Wishlist for WooCommerce plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.1.10. This is due to a missing capability check on the deleteWishlist() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary 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 confidence

The Premmerce Wishlist for WooCommerce plugin has a missing authorization vulnerability in the deleteWishlist() function. Any authenticated user with Subscriber-level access or higher can delete arbitrary wishlists in the system due to a missing capability check, allowing unauthorized modification of wishlist data.

MitigationUpdate to version 1.1.11 or later which should include proper capability checks on the deleteWishlist function, or implement a current_user_can() check before allowing wishlist deletion.

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. Identify if Premmerce Wishlist for WooCommerce is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the premmerce-wishlist-for-woocommerce folder, or look for the plugin in WP Admin > Plugins
    Affected if The plugin folder premmerce-wishlist-for-woocommerce exists in the plugins directory
  2. Check the installed plugin version
    In WP Admin > Plugins, find the Premmerce Wishlist for WooCommerce entry and read the version number from the plugin description, or check the plugin main PHP file for the 'Version' header comment
    Affected if The installed version is lower than 1.1.11
  3. Verify the deleteWishlist function has capability checks
    Access the plugin source code and locate the deleteWishlist() function (typically in includes/ajax.php or similar). Search for current_user_can() or a capability check before executing the deletion logic
    Affected if No current_user_can() or capability check is found before the wishlist deletion code executes
  4. Confirm subscriber role has access to wishlist deletion
    In WP Admin > Users > Roles, verify that the Subscriber role exists and has not been restricted from accessing the plugin's AJAX endpoints, or test by logging in as a subscriber and attempting to access the delete wishlist AJAX action via wp-admin/admin-ajax.php
    Affected if Subscriber role users can access and successfully execute the wishlist deletion without receiving a capability denied error

You are affected if the Premmerce Wishlist for WooCommerce plugin is installed with a version below 1.1.11 and the deleteWishlist function lacks proper capability verification, allowing any authenticated subscriber-level user to delete arbitrary wishlists.

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 1.1.11 or later which should include proper capability checks on the deleteWishlist function, or implement a current_user_can() check before allowing wishlist deletion.

Recommended fix High confidence

Version 1.1.11 or later

  1. Check the current version of the Premmerce Wishlist for WooCommerce plugin installed on the WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate Premmerce Wishlist for WooCommerce and note the current version
  4. Navigate to Plugins > Add New > Upload Plugin or check for updates via Plugins > Plugin Updates
  5. Update to the latest available version of the plugin (version 1.1.11 or later, as versions up to and including 1.1.10 are affected)
  6. Verify the update completed successfully
  7. Test that wishlist functionality works correctly after the update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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