dbcve.org
Woocommerce WishlistWordPress extension · Moreconvert

CVE-2024-34819

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 1.7.3 or later.
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
Missing Authorization vulnerability in Moreconvert Team MC Woocommerce Wishlist smart-wishlist-for-more-convert.This issue affects MC Woocommerce Wishlist: from n/a through <= 1.7.2.

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 MC Woocommerce Wishlist plugin allows unauthenticated or unauthorized users to access or manipulate wishlist data that should require proper capability checks. This typically occurs when AJAX endpoints or actions lack proper current_user_can() verification before performing operations on user wishlists.

MitigationAdd proper capability checks and authorization validation to all AJAX handlers and public-facing functions that access or modify wishlist data, ensuring only authenticated users with appropriate permissions can view or edit their own wishlists.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Woocommerce WishlistWordPress extension
Affected:< 1.7.3

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 the plugin is installed
    Inspect the WordPress plugins directory at wp-content/plugins/ for a folder containing 'moreconvert' and 'wishlist' in the name, or list all installed plugins via the WordPress admin dashboard under Plugins.
    Affected if The Moreconvert Woocommerce Wishlist plugin appears in the installed plugins list.
  2. Determine the installed plugin version
    Access the Plugins page in WordPress admin and locate the Moreconvert Woocommerce Wishlist entry, or open the main plugin PHP file (typically the primary file in the plugin folder) and look for the 'Version' header in the plugin comment block.
    Affected if The version number displayed is lower than 1.7.3 (for example, 1.7.2, 1.7.1, 1.0.0, etc.).
  3. Verify the plugin is active
    Check the WordPress Plugins admin page to confirm the Moreconvert Woocommerce Wishlist plugin has the 'Active' status indicator.
    Affected if The plugin is currently activated on the WordPress site.
  4. Confirm AJAX endpoints lack capability checks
    Review the plugin PHP files (particularly any file handling AJAX requests, often named ajax.php or containing wp_ajax_ hooks) and search for the presence of current_user_can() calls before wishlist data operations. If the plugin code cannot be directly reviewed, test by attempting to access wishlist functionality as an unauthenticated visitor.
    Affected if AJAX actions related to wishlist operations do not contain current_user_can() verification, or unauthenticated users can successfully submit requests to wishlist AJAX endpoints.

If the Moreconvert Woocommerce Wishlist plugin is installed, active, and running at a version lower than 1.7.3, the environment is affected by this authorization bypass vulnerability.

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
Upgrade available Upgrade to 1.7.3 or later
Fixed in 1.7.3
Interim mitigation

Add proper capability checks and authorization validation to all AJAX handlers and public-facing functions that access or modify wishlist data, ensuring only authenticated users with appropriate permissions can view or edit their own wishlists.

Recommended fix High confidence

1.7.3

  1. Back up your WordPress site and database before making any changes
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Find 'MC Woocommerce Wishlist' (also known as 'smart-wishlist-for-more-convert') in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 1.7.3 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify the plugin version shows 1.7.3 in the Plugins list
  6. Test that the wishlist functionality works correctly on the frontend

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

Fix this in Woocommerce Wishlist 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 the upgrade done

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-2024-34819 — 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-2024-34819 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