dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-14541

HIGH · 7.2 CVSS v3.1 Published 2026-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 Lucky Wheel Giveaway plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.0.22 via the conditional_tags parameter. This is due to the plugin using PHP's eval() function on user-controlled input without proper validation or sanitization. This makes it possible for authenticated attackers, with Administrator-level access and above, to execute code on the server.

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 Lucky Wheel Giveaway WordPress plugin (versions up to 1.0.22) uses PHP's eval() function on the conditional_tags parameter without sanitizing user input. This allows authenticated administrators to execute arbitrary PHP code on the server by injecting malicious code through this parameter.

MitigationUpdate to version 1.0.23 or later which removes the vulnerable eval() usage. If an update is unavailable, consider removing the plugin until a patched version is released.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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. Locate the Lucky Wheel Giveaway plugin installation
    Check your WordPress plugins directory (typically wp-content/plugins/lucky-wheel-giveaway/) or view the installed plugins list in WordPress admin under Plugins.
    Affected if The plugin folder lucky-wheel-giveaway exists in your plugins directory.
  2. Determine the installed plugin version
    Open the main plugin file (usually lucky-wheel-giveaway.php) and look for the version comment in the plugin header, or check the readme.txt file for the Version field.
    Affected if The version number is 1.0.22 or lower.
  3. Verify the vulnerable eval() code is present
    Search the plugin source files for the string 'eval(' and specifically look for usage involving 'conditional_tags' parameter.
    Affected if Code contains eval() being called on the conditional_tags parameter without sanitization.
  4. Confirm administrator access is available
    Check if any user accounts with Administrator role exist in WordPress (Users > All Users in admin), as this vulnerability requires admin-level authentication.
    Affected if At least one Administrator-level user account exists and can access the plugin settings.

You are affected if the Lucky Wheel Giveaway plugin is installed with version 1.0.22 or lower, contains eval() on the conditional_tags parameter, and an administrator account can access the plugin configuration.

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 version 1.0.23 or later which removes the vulnerable eval() usage. If an update is unavailable, consider removing the plugin until a patched version is released.

Recommended fix Moderate confidence

Lucky Wheel Giveaway version 1.0.23 or latest available version

  1. 1. Log in to the WordPress admin dashboard with Administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Lucky Wheel Giveaway' plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running version 1.0.23 or higher
  6. 6. Test the plugin's core functionality (wheel spinning, prize configuration) to ensure the update did not break expected features
Caveat Review plugin settings after upgrade as minor configuration adjustments may be needed

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 / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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