dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-58247

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-22
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
Missing Authorization vulnerability in templateinvaders TI WooCommerce Wishlist ti-woocommerce-wishlist allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects TI WooCommerce Wishlist: from n/a through <= 2.10.0.

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 TI WooCommerce Wishlist plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to wishlist functionality or data without proper authentication.

MitigationUpdate to the latest patched version of TI WooCommerce Wishlist when released, or implement proper authorization checks on all wishlist-related endpoints and functions.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 TI WooCommerce Wishlist plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'TI WooCommerce Wishlist' - the version number is displayed below the plugin name. Alternatively, check the main plugin file header or the readme.txt file in the plugin directory.
    Affected if Installed version is lower than the latest patched version available from the vendor
  2. Verify wishlist REST API endpoints require authentication
    Send a GET request to the wishlist REST API endpoint (typically /wp-json/ti-wishlist/v1/ or /wp-json/wishlist/v1/) without providing authentication credentials. Use a tool like curl or browser DevTools to inspect the response.
    Affected if The API returns sensitive wishlist data or allows wishlist operations without requiring valid authentication tokens
  3. Test wishlist page access without login
    Open the wishlist page URL (commonly /wishlist/ or as configured in plugin settings) in an incognito browser window without being logged in. Attempt to view, add, or modify wishlist items.
    Affected if The wishlist page displays private user wishlists or allows modifications without being logged in or providing valid user credentials
  4. Check for publicly accessible wishlist AJAX actions
    Examine the site for AJAX endpoints used by the plugin (typically in /wp-admin/admin-ajax.php?action=). Test common wishlist actions like add_to_wishlist, remove_from_wishlist, or get_wishlist without authentication.
    Affected if AJAX actions complete successfully and return or modify wishlist data without requiring user authentication

User is affected if the TI WooCommerce Wishlist plugin version is unpatched AND wishlist functionality is accessible to unauthenticated users.

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 latest patched version of TI WooCommerce Wishlist when released, or implement proper authorization checks on all wishlist-related endpoints and functions.

Recommended fix Moderate confidence

Latest stable version of TI WooCommerce Wishlist (verify current fixed release on wordpress.org or vendor site)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Check the current version of TI WooCommerce Wishlist plugin installed on your site
  3. 3. Navigate to Plugins > Installed Plugins in WordPress admin
  4. 4. If an update is available for TI WooCommerce Wishlist, click Update Now
  5. 5. Alternatively, download the latest version from the WordPress plugin repository or from the developer's official site
  6. 6. After updating, verify the plugin version matches the latest stable release
  7. 7. Test critical wishlist functionality (add to wishlist, view wishlist, remove from wishlist) to ensure the update did not break existing functionality
  8. 8. Review user roles and capabilities to ensure authorization controls are properly configured
Caveat Minor risk - verify compatibility with your WooCommerce version before updating

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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