dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-2052

HIGH · 8.8 CVSS v3.1 Published 2026-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
The Widget Options – Advanced Conditional Visibility for Gutenberg Blocks & Classic Widgets plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.2.2 via the Display Logic feature. This is due to the plugin using eval() on user-supplied Display Logic expressions with an insufficient blocklist/allowlist that can be bypassed using array_map with string concatenation, combined with a lack of authorization enforcement on the extended_widget_opts_block attribute. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server. The vulnerability was partially patched in version 4.2.0.

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 Widget Options WordPress plugin uses eval() on user-supplied Display Logic expressions with an insufficient blocklist that can be bypassed using array_map with string concatenation, combined with missing authorization checks on the extended_widget_opts_block attribute. This allows authenticated Contributor+ users to execute arbitrary PHP code on the server.

MitigationUpdate the Widget Options plugin to the latest version immediately. Until patched, consider restricting user capabilities and monitoring for suspicious Display Logic attribute modifications.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Widget Options plugin is installed
    Check wp-content/plugins/widget-options/ directory exists, or look for 'Widget Options' in WordPress admin Plugins list
    Affected if Plugin is installed and active
  2. Determine installed Widget Options version
    Read the main plugin PHP file header (e.g., widget-options.php) for 'Version:' value, or check in WordPress admin Plugins > Installed Plugins
    Affected if Version matches or falls within the affected version range (compare your installed version to known vulnerable versions)
  3. Confirm Display Logic feature is in use
    Check widget settings in Appearance > Widgets for any widgets using 'Display Logic' option, or inspect page source for 'widget_opts[display_logic]' parameters
    Affected if Display Logic is configured on any active widget
  4. Verify extended_widget_opts_block attribute accessibility
    Inspect HTML forms in wp-admin/widgets.php for 'extended_widget_opts_block' input fields, or check widget option forms for this hidden field
    Affected if extended_widget_opts_block attribute is present in widget configuration forms

User is affected if Widget Options plugin is installed with a vulnerable version AND Display Logic feature is enabled on any widget, making the eval() on user-supplied input reachable.

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 the Widget Options plugin to the latest version immediately. Until patched, consider restricting user capabilities and monitoring for suspicious Display Logic attribute modifications.

Recommended fix Moderate confidence

Upgrade to the latest version of the Widget Options plugin (currently 4.2.3 or higher on wordpress.org)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Widget Options – Advanced Conditional Visibility for Gutenberg Blocks & Classic Widgets' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/widget-options/ and upload manually
  6. 6. After updating, verify the Display Logic feature no longer uses eval() by reviewing plugin code if possible
  7. 7. Consider reviewing user access levels and removing the 'extend_widget_opts_block' capability from lower-privileged roles as an additional precaution
Caveat Minimal risk - standard plugin update; ensure a backup before updating

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 / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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