dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-10567

HIGH · 7.5 CVSS v3.1 Published 2024-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 TI WooCommerce Wishlist plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wizard' function in all versions up to, and including, 2.9.1. This makes it possible for unauthenticated attackers to create new pages, modify plugin settings, and perform limited options updates.

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 TI WooCommerce Wishlist WordPress plugin versions up to 2.9.1 lacks a capability check on the 'wizard' function, allowing unauthenticated attackers to access an administrative function. This Broken Access Control vulnerability enables creation of arbitrary pages, modification of plugin settings, and limited WordPress options updates.

MitigationUpgrade the TI WooCommerce Wishlist plugin to version 2.9.2 or later which includes proper capability verification on the wizard function. Until patched, consider restricting access to the affected endpoint via web server configuration or disabling the plugin if immediate patching is not feasible.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Check installed TI WooCommerce Wishlist version
    In WordPress admin, go to Plugins > Installed Plugins > TI WooCommerce Wishlist and note the version number. Alternatively, check the plugin file header in wp-content/plugins/woocommerce-ti-wishlist/ti-woocommerce-wishlist.php or use WP-CLI: wp plugin list --name='woocommerce-ti-wishlist'
    Affected if Version is 2.9.1 or lower (any version up to and including 2.9.1)
  2. Verify unauthenticated access to wizard endpoint
    Send a GET or POST request to the endpoint containing 'wizard' in the URL path, such as /?wizard=1 or /wp-admin/admin-ajax.php?action=wizard (the exact endpoint varies based on plugin configuration). Use a non-authenticated browser or curl: curl -s 'https://your-site.com/?wizard=1'
    Affected if The request returns a response containing plugin administrative functionality, settings forms, or page creation interfaces without requiring login
  3. Check for newly created wishlist pages
    In WordPress admin, go to Pages > All Pages and look for unexpected pages with titles related to wishlist setup, wizard, or plugin configuration that were not created by legitimate administrators
    Affected if Unexpected pages exist that correspond to wizard-generated content
  4. Inspect plugin settings for unauthorized modifications
    Navigate to Wishlist > Settings in the WordPress admin and review all settings tabs (general, products, page, etc.) for any changes made by unauthenticated attackers, or check the wp_options table for recent modifications to wishlist-related options
    Affected if Settings have been altered without administrator action or option values in wp_options show recent unauthorized changes

You are affected if the TI WooCommerce Wishlist plugin version is 2.9.1 or lower AND the wizard endpoint is accessible without authentication, allowing arbitrary page creation or settings modification.

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

Upgrade the TI WooCommerce Wishlist plugin to version 2.9.2 or later which includes proper capability verification on the wizard function. Until patched, consider restricting access to the affected endpoint via web server configuration or disabling the plugin if immediate patching is not feasible.

Recommended fix Moderate confidence

Update to the latest version of TI WooCommerce Wishlist (version higher than 2.9.1)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the TI WooCommerce Wishlist plugin.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Verify the update was successful by checking the plugin version after updating.
  6. 6. Test that the wishlist functionality works correctly on your site after the update.
  7. 7. Consider reviewing user roles and capabilities to ensure proper authorization controls are in place.
Caveat Minor: Review any customizations or integrations with the wishlist functionality after upgrading to ensure compatibility

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