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-2026-0808: CWE-602 Client-Side Enforcement of Server-Side Security in bdthemes Spin Wheel – Interactive spinning wheel that offers coupons

0
Medium
VulnerabilityCVE-2026-0808cvecve-2026-0808cwe-602
Published: Sat Jan 17 2026 (01/17/2026, 06:42:20 UTC)
Source: CVE Database V5
Vendor/Project: bdthemes
Product: Spin Wheel – Interactive spinning wheel that offers coupons

Description

The Spin Wheel plugin for WordPress is vulnerable to client-side prize manipulation in all versions up to, and including, 2.1.0. This is due to the plugin trusting client-supplied prize selection data without server-side validation or randomization. This makes it possible for unauthenticated attackers to manipulate which prize they win by modifying the 'prize_index' parameter sent to the server, allowing them to always select the most valuable prizes.

AI-Powered Analysis

AILast updated: 01/17/2026, 07:06:14 UTC

Technical Analysis

The vulnerability identified as CVE-2026-0808 affects the Spin Wheel – Interactive spinning wheel plugin developed by bdthemes for WordPress, which is widely used to engage customers by offering coupons through a gamified spinning wheel interface. The core issue is a client-side enforcement of what should be server-side security controls, classified under CWE-602. Specifically, the plugin trusts the 'prize_index' parameter sent from the client to determine the prize awarded, without performing any server-side validation or randomization. This design flaw allows an unauthenticated attacker to manipulate the parameter value directly, thereby selecting any prize they desire, including the most valuable ones. The vulnerability affects all versions up to and including 2.1.0. The CVSS 3.1 base score is 5.3 (medium severity), reflecting that the attack vector is network-based (AV:N), requires no privileges (PR:N), and no user interaction (UI:N), but impacts only integrity (I:L) without affecting confidentiality or availability. No patches or fixes are currently linked, and no known exploits have been reported in the wild. The vulnerability undermines the fairness and trustworthiness of promotional campaigns using the plugin, potentially leading to financial losses and brand damage. The lack of server-side controls is a fundamental security oversight that should be addressed by plugin developers and site administrators.

Potential Impact

For European organizations, especially those operating e-commerce platforms or marketing campaigns using WordPress and the Spin Wheel plugin, this vulnerability can lead to unauthorized prize redemptions, resulting in financial losses and erosion of customer trust. The integrity of promotional offers is compromised, which may affect customer loyalty and brand reputation. Although the vulnerability does not expose sensitive data or disrupt service availability, the ability for attackers to consistently win high-value coupons can cause direct economic harm. Additionally, organizations may face regulatory scrutiny under consumer protection laws if promotional fairness is violated. The impact is more pronounced for businesses heavily reliant on digital marketing and customer engagement tools. Attackers exploiting this flaw could also skew analytics and campaign effectiveness metrics, leading to misguided business decisions.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately verify if their WordPress sites use the Spin Wheel plugin version 2.1.0 or earlier and disable or remove the plugin if no update is available. Since no official patch links are provided, administrators should implement server-side validation to ensure that the 'prize_index' parameter cannot be arbitrarily set by clients. This includes generating the prize outcome server-side using secure randomization methods and ignoring client-supplied prize data. Monitoring and logging prize redemption patterns can help detect anomalies indicative of exploitation. Additionally, organizations should consider implementing rate limiting and CAPTCHA challenges to reduce automated abuse. Engaging with the plugin vendor for an official fix or security update is critical. Finally, educating marketing and IT teams about this risk will help in early detection and response.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-01-09T14:36:32.229Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 696b3178b22c7ad86896536b

Added to database: 1/17/2026, 6:51:36 AM

Last enriched: 1/17/2026, 7:06:14 AM

Last updated: 1/17/2026, 8:12:24 AM

Views: 6

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