Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12427: CWE-639 Authorization Bypass Through User-Controlled Key in yithemes YITH WooCommerce Wishlist

0
Medium
VulnerabilityCVE-2025-12427cvecve-2025-12427cwe-639
Published: Wed Nov 19 2025 (11/19/2025, 03:29:39 UTC)
Source: CVE Database V5
Vendor/Project: yithemes
Product: YITH WooCommerce Wishlist

Description

The YITH WooCommerce Wishlist plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.10.0 via the REST API endpoint and AJAX handler due to missing validation on user-controlled keys. This makes it possible for unauthenticated attackers to discover any user's wishlist token ID, and subsequently rename the victim's wishlist without authorization (integrity impact). This can be exploited to target multi-user stores for defacement, social engineering attacks, mass tampering, and profiling at scale.

AI-Powered Analysis

AILast updated: 11/26/2025, 04:44:07 UTC

Technical Analysis

CVE-2025-12427 is an authorization bypass vulnerability classified under CWE-639 (Authorization Bypass Through User-Controlled Key) affecting the YITH WooCommerce Wishlist plugin for WordPress, versions up to and including 4.10.0. The flaw exists in the REST API endpoint and AJAX handler where the plugin fails to properly validate user-supplied wishlist token IDs. This lack of validation allows unauthenticated attackers to enumerate or guess valid wishlist token IDs belonging to other users. Once a valid token ID is identified, the attacker can rename the victim's wishlist without any authorization checks, thereby compromising the integrity of the wishlist data. The vulnerability does not expose confidential information nor does it affect system availability, but it enables attackers to manipulate user data, potentially leading to defacement of user content, social engineering attacks by altering wishlist names, and profiling of users at scale. The attack vector requires no authentication or user interaction, and the vulnerability is remotely exploitable over the network. Although no public exploits have been reported, the medium CVSS score of 5.3 reflects the moderate impact and ease of exploitation. The vulnerability affects all versions of the plugin up to 4.10.0, and no official patches are currently linked, indicating that users must monitor vendor updates closely. The flaw is particularly concerning for multi-user WooCommerce stores where wishlists are a key feature for user engagement and marketing.

Potential Impact

For European organizations operating WooCommerce-based e-commerce platforms using the vulnerable YITH WooCommerce Wishlist plugin, this vulnerability poses a risk to the integrity of user-generated content. Attackers can rename wishlists arbitrarily, which could lead to customer confusion, damage to brand reputation, and potential loss of customer trust. The ability to tamper with wishlists at scale also opens avenues for social engineering attacks, where attackers might manipulate wishlist names to mislead users or inject malicious links. Although no direct data leakage or service disruption occurs, the reputational and operational impacts could be significant, especially for large retailers and marketplaces relying on WooCommerce in Europe. Furthermore, attackers could profile users by enumerating wishlist tokens, potentially aiding targeted phishing or fraud campaigns. This risk is amplified in countries with high WooCommerce market penetration and where e-commerce regulations emphasize data integrity and consumer protection. Organizations may face regulatory scrutiny if user data integrity is compromised, even without direct data breaches.

Mitigation Recommendations

European organizations should immediately audit their WordPress installations to identify the presence and version of the YITH WooCommerce Wishlist plugin. Until an official patch is released, administrators should consider disabling the wishlist functionality or restricting access to the REST API and AJAX endpoints related to wishlists via web application firewalls (WAFs) or server-level access controls. Implementing strict server-side validation to verify that any wishlist token ID corresponds to the authenticated user before allowing modifications is critical. Monitoring logs for unusual activity targeting wishlist endpoints can help detect exploitation attempts. Organizations should also educate their development teams to follow secure coding practices, particularly validating and authorizing user inputs in REST API handlers. Once a vendor patch is available, prompt application of updates is essential. Additionally, consider implementing rate limiting on API endpoints to reduce the risk of token enumeration. Finally, communicate transparently with customers about any potential impact and remediation steps to maintain trust.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-28T19:57:51.583Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 691d3cbbc00dea8b9c9becb3

Added to database: 11/19/2025, 3:42:51 AM

Last enriched: 11/26/2025, 4:44:07 AM

Last updated: 1/7/2026, 8:53:21 AM

Views: 62

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats