dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-49319

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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
Missing Authorization vulnerability in WPFactory Wishlist for WooCommerce wish-list-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Wishlist for WooCommerce: from n/a through <= 3.2.3.

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 · moderate confidence

Missing authorization vulnerability in the Wishlist for WooCommerce plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to or modification of wishlist data that should be restricted to privileged users.

MitigationUpdate to the patched version of Wishlist for WooCommerce once available; until then, restrict access to the plugin's endpoints via web server configuration or temporarily disable the plugin if high-risk.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 Wishlist for WooCommerce plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Wishlist for WooCommerce' in the installed plugins list, or search the wp-content/plugins directory for a folder containing 'woocommerce-wishlist' or similar wishlist-related plugin files
    Affected if The plugin is installed and active on the WooCommerce site
  2. Identify installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find the Wishlist for WooCommerce plugin and note the version number displayed under the plugin name; alternatively, open the main plugin PHP file and look for the 'Version' header in the plugin comments
    Affected if The installed version has not received a security patch for CVE-2025-49319 (compare against the version that includes the fix)
  3. Identify plugin AJAX and REST endpoints
    Examine the plugin directory for PHP files containing 'add_action' calls registering AJAX handlers (wp_ajax_*) or REST API routes, noting their endpoint names; common paths include includes/class-ajax.php or api/ endpoints within the plugin folder
    Affected if The plugin exposes endpoints that handle wishlist data without visible capability checks
  4. Test for unauthorized access to wishlist data
    Using a tool like curl or Burp Suite, send requests to the plugin's AJAX or REST endpoints (such as those adding/removing products from wishlists or retrieving other users' wishlists) without providing authentication credentials or with a low-privilege user account
    Affected if The endpoints return or modify wishlist data without requiring proper authorization or capability verification
  5. Verify access control implementation
    Review the plugin source code for the identified endpoints, specifically looking for current_user_can() or wp_verify_nonce() calls before executing wishlist operations; check if capability checks like 'manage_options' or 'edit_products' are properly applied to all data modification and retrieval functions
    Affected if Endpoints lack proper authorization checks or use weak capability verifications that allow unauthenticated or low-privileged users to access restricted wishlist data

A user is affected if the Wishlist for WooCommerce plugin is installed and its endpoints allow unauthorized access to or modification of wishlist data due to missing or inadequate authorization controls.

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 the patched version of Wishlist for WooCommerce once available; until then, restrict access to the plugin's endpoints via web server configuration or temporarily disable the plugin if high-risk.

Recommended fix Moderate confidence

Latest version of Wishlist for WooCommerce (version > 3.2.3)

  1. Check the plugin's WordPress repository or WPFactory official site for the latest version of Wishlist for WooCommerce
  2. Update the plugin to the latest available version that includes the security fix
  3. Verify the update was successful and test wishlist functionality

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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