dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-32222

CRITICAL · 9.9 CVSS v3.1 Published 2025-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Control of Generation of Code ('Code Injection') vulnerability in Widgetlogic.org Widget Logic widget-logic allows Code Injection.This issue affects Widget Logic: from n/a through <= 6.0.5.

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

A code injection vulnerability in the Widget Logic WordPress plugin (versions <= 6.0.5) allows attackers to inject malicious PHP code through the plugin's widget logic/condition settings, potentially achieving remote code execution on the affected WordPress installation.

MitigationUpdate Widget Logic to the latest version immediately; if an updated patch is unavailable, disable the plugin entirely and consider the site potentially compromised given the critical (9.9) CVSS severity.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Verify Widget Logic plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate Widget Logic, or check the /wp-content/plugins/ directory for the widget-logic folder
    Affected if The plugin is present on the WordPress installation
  2. Check the installed version number
    In the plugins list in WordPress admin, look at the version number displayed under the Widget Logic plugin name, or read the main plugin file (usually widget-logic.php) and locate the Version header comment
    Affected if The version is 6.0.5 or lower (any version <= 6.0.5)
  3. Determine if PHP execution is enabled in settings
    Go to Appearance > Widgets in the WordPress admin. Open any widget that uses Widget Logic. Look for the widget logic field and check if the 'Execute PHP' checkbox option is enabled, or inspect the 'widget_logic' option in the wp_options database table for the 'execute_php' setting set to 1
    Affected if The Execute PHP option is enabled, as this is the attack vector that allows injected PHP code to run
  4. Review widget logic entries for suspicious code
    In the WordPress admin under Appearance > Widgets, examine all widgets with widget logic conditions populated. Also inspect the wp_options table for rows where option_name = 'widget_logic' and review the option_value for any encoded or obfuscated PHP functions such as eval(), base64_decode(), shell_exec(), system(), or preg_replace with /e modifier
    Affected if Any widget logic field contains PHP code (particularly eval, base64_decode, shell_exec, system, or similar remote code execution functions)
  5. Check for unauthorized admin accounts or file modifications
    Review Users > All Users in WordPress admin for unknown administrator accounts, and compare file integrity of the /wp-content/plugins/widget-logic/ directory against a known good backup or the WordPress plugin repository version
    Affected if New admin accounts exist or plugin files have been modified from the original distribution

A WordPress site is affected if Widget Logic plugin version 6.0.5 or lower is installed AND the Execute PHP option is enabled in the widget settings, allowing attackers to inject malicious PHP code through widget logic conditions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Widget Logic to the latest version immediately; if an updated patch is unavailable, disable the plugin entirely and consider the site potentially compromised given the critical (9.9) CVSS severity.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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