CVE-2026-2052 HIGH

CVE-2026-2052: Widget Options <= 4.2.2 - Authenticated (Contributor+) Remote Code Execution via Display Logic

Vendor Marketingfire
Product Widget Options – Advanced Conditional Visibility for Gutenberg Blocks & Classic Widgets
Weakness CWE-94 · Code injection
Published May 2, 2026
Last update May 4, 2026

CVSS base score

8.8/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity High

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

The Widget Options plugin for WordPress contains a code injection vulnerability in versions up to 4.2.2. An authenticated user with low privileges can inject and execute arbitrary PHP code on the site by manipulating plugin settings. This allows complete compromise of the WordPress installation, including data theft, malware installation, and site defacement.

What an attacker can do

03Attacker Capabilities

Run arbitrary PHP code on the site and access all data, modify content, or install malware.

Potential impact on your site

04Site Impact

Any low-privilege user account can take over the entire site. Immediate account audit and code review required.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress user account (e.g., contributor or subscriber role).

Key dates

06Disclosure timeline

May 2, 2026 CVE published
May 4, 2026 Record updated