Skip to main content

WooCommerce Lucky Wheel CVE-2025-14509

HIGH
Code Injection (CWE-94)
2025-12-30 security@wordfence.com
7.2
CVSS 3.1 · Vendor: wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain Administrator/Site-Admin access
  2. Delivery
    Open Lucky Wheel settings
  3. Exploit
    Inject PHP into 'Conditional Tags'
  4. Execution
    Plugin passes input to eval()
  5. Impact
    Arbitrary PHP executes on server

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires authenticated access at WordPress Administrator level or above (PR:H) and the Lucky Wheel for WooCommerce plugin version ≤1.1.13 installed. The specific prerequisite is the ability to set the plugin's 'Conditional Tags' configuration value, which is then passed to eval(). The main limiting factor is the Administrator privilege requirement - on single-site installs such a user typically already has code-execution capability via the file editor, so the practical escalation is marginal there; the meaningful exposure is in multisite environments where Site Administrators are intentionally barred from editing plugin/theme files, making this a privilege-boundary bypass. No user interaction is needed once the setting is saved.

Impact

This is a genuine remote code execution flaw (CWE-94) but its real-world priority is tempered by a high privilege requirement. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, score 7.2) confirms network vector, low complexity, no user interaction, and full confidentiality/integrity/availability impact - but PR:H means the attacker must already hold Administrator-level access. On a standard single-site WordPress install, an administrator can normally already edit plugin/theme files and achieve code execution, so this vulnerability adds little marginal risk there; its true significance is in the multisite scenario the description calls out, where Site Administrators are deliberately denied file-editing yet can abuse the eval() sink to cross that privilege boundary. There is no EPSS score, no CISA KEV listing, and no public exploit identified at time of analysis, which is consistent with a hard-to-reach, admin-gated bug that mass-exploitation tooling would not target. No SSVC decision data was supplied. No conflicting signals were found: the description (admin-level) and the CVSS PR:H are in agreement, unlike many Wordfence advisories.

Exploit ScenarioDerived

An attacker who has obtained WordPress Administrator (or, in multisite, Site Administrator) credentials navigates to the Lucky Wheel plugin settings and enters crafted PHP into the 'Conditional Tags' field, which is passed to eval() at frontend/frontend.php line 127 without sanitization. When the relevant frontend logic executes, the attacker's PHP runs on the server, yielding full code execution. No public proof-of-concept is currently identified, and exploitation requires pre-existing high privileges.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 01, 2026

PHP code execution in the WooCommerce Lucky Wheel plugin (versions up to and including 1.1.13) allows an authenticated attacker with Administrator-level access to run arbitrary PHP on the server by setting the plugin's 'Conditional Tags' option, which is passed unsafely to eval(). The flaw is most impactful on WordPress multisite installations, where Site Administrators-who are normally blocked from editing plugin or theme files-can bypass that boundary to achieve code execution. No public exploit identified at time of analysis; an upstream fix is available via changeset 3428063, though a specific patched version has not been confirmed.

RemediationAI

Apply the upstream fix by updating the plugin to a version later than 1.1.13 once the vendor releases it; the changeset 3428063 (https://plugins.trac.wordpress.org/changeset/3428063/) appears to address the eval() call, but the exact patched version is not confirmed in the provided data. If an update is not immediately available, disable the plugin entirely-no configuration change within the plugin can safely mitigate the code injection. On WordPress multisite installations, restrict access to the plugin's settings page to Super Admins only as a temporary compensating control, but this does not fix the underlying flaw if a Site Admin can still set the 'Conditional Tags' option. Monitor the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/9a41bc0e-0ab9-4cee-b3ca-d730c828782c?source=cve) and the plugin's Trac page for the patched release. Note that on single-site installations, the practical risk is low because Administrators already have code-execution capability; prioritize multisite environments where the vulnerability enables a privilege escalation.

Affected ProductsAI

Affected product: Lucky Wheel for WooCommerce - Spin a Sale plugin for WordPress, all versions up to and including 1.1.13. The vulnerable code is in the frontend/frontend.php file at line 127, per the Trac references (https://plugins.trac.wordpress.org/browser/woo-lucky-wheel/tags/1.1.13/frontend/frontend.php#L127 and trunk). No CPE string was supplied. The vendor's plugin repository is at https://plugins.trac.wordpress.org/browser/woo-lucky-wheel/, and the fix changeset is https://plugins.trac.wordpress.org/changeset/3428063/.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is a PHP code injection (CWE-94) in the Lucky Wheel for WooCommerce - Spin a Sale plugin. The plugin takes the value of the 'Conditional Tags' setting and passes it directly to PHP's eval() function without validation or sanitization, as shown in frontend/frontend.php line 127. This allows any code in that setting to be executed as PHP on the server. The attack vector is network-based (AV:N) with low complexity (AC:L) and no user interaction (UI:N), but it requires high privileges (PR:H). The primary risk is not on single-site WordPress installations-where Administrators already have the ability to edit plugin files-but on multisite networks, where the same role is deliberately restricted from file editing; the flaw thus enables a privilege-boundary bypass. No CPE string was provided in the input data.

Know when PHP gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (wordfence) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.2 HIGH

Admin-level access is required to reach the vulnerable 'Conditional Tags' eval() sink, so PR:H; the resulting arbitrary PHP execution grants full host CIA impact.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (wordfence).

CVSS VectorVendor: wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

The Lucky Wheel for WooCommerce - Spin a Sale plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 1.1.13. This is due to the plugin using eval() to execute user-supplied input from the 'Conditional Tags' setting without proper validation or sanitization. This makes it possible for authenticated attackers, with Administrator-level access and above, to execute arbitrary PHP code on the server. In WordPress multisite installations, this allows Site Administrators to execute arbitrary code, a capability they should not have since plugin/theme file editing is disabled for non-Super Admins in multisite environments.

Executive ViewAI

Why It Matters

A high-severity PHP code execution flaw in the WooCommerce Lucky Wheel plugin (versions up to and including 1.1.13) lets a WordPress Administrator-level user - including a Site Administrator on a multisite network who is normally prevented from touching plugin or theme files - execute arbitrary code on the underlying server. No vendor patch is currently available, so every site still running the affected plugin should be considered exposed until it is removed or otherwise mitigated. Leadership should care because an over-privileged or compromised administrator account can now escalate to full server compromise, endangering customer data, order and payment flows, and every other site hosted on shared infrastructure.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; the upstream fix is referenced by changeset 3428063 but a specific patched version has not been confirmed. Interim mitigations: deactivate and remove the WooCommerce Lucky Wheel plugin (up to and including 1.1.13) where business use is not essential; restrict and audit Administrator and Site Administrator accounts, enforce least privilege, MFA and credential rotation; on WordPress multisite, treat Site Administrator as a privileged role and review network-level permissions; inspect and lock down the plugin's 'Conditional Tags' option; deploy WAF or virtual patching rules blocking unauthorized changes to that option; enable file integrity monitoring and PHP write alerts; and monitor logs for unexpected code execution activity.

Threat Intelligence Overview

EPSS Score
0.6%
Top 51% exploitable
Prevalence
Low
niche WooCommerce spin-the-wheel gamification plugin, limited install base
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.6%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

37
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy