Skip to main content

Widget Options EUVDEUVD-2026-26754

| CVE-2026-2052 HIGH
Code Injection (CWE-94)
2026-05-02 Wordfence
8.8
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

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

  1. Recon
    Obtain Contributor credentials
  2. Delivery
    Access WordPress admin panel
  3. Exploit
    Create/edit Gutenberg block or widget
  4. Install
    Inject eval() bypass payload in Display Logic
  5. C2
    Trigger server-side evaluation
  6. Execute
    Execute arbitrary PHP code
  7. Impact
    Deploy web shell for persistence

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 to the target WordPress installation with at least Contributor-level privileges (PR:L), which grants the ability to create and edit posts/blocks but not publish them without approval. The Display Logic feature must be actively used or available in the Widget Options plugin installation. Exploitation specifically targets the extended_widget_opts_block attribute which lacks proper authorization enforcement, meaning Contributor users can supply malicious expressions that should be restricted to Administrators. No user interaction required (UI:N) once the attacker has Contributor access. The vulnerability is not exploitable against default WordPress configurations that do not have the Widget Options plugin installed, and is limited to WordPress environments specifically using this third-party plugin for widget conditional visibility management. Sites that do not permit Contributor registration or tightly control user role assignments reduce the attack surface but remain vulnerable if Contributor accounts exist.

Impact

The CVSS v3.1 score of 8.8 (High) reflects the severe technical impact (complete confidentiality, integrity, and availability compromise) with straightforward exploitation requirements (AV:N/AC:L/PR:L/UI:N). Attack complexity is low and requires only low-privilege authentication (Contributor role), making this exploitable by users who can create draft posts in WordPress. No EPSS score provided for probability assessment, and no CISA KEV listing indicates this is not confirmed as actively exploited in the wild. However, the partial patch in version 4.2.0 followed by additional fixes in changesets 3481338 and 3514411 suggests ongoing remediation efforts, indicating the vulnerability may still be present in intermediate versions. Real-world risk is HIGH for WordPress sites where Contributor-level accounts exist (common in multi-author blogs, news sites, community platforms) because the privilege requirement is minimal and the impact is total system compromise. The absence of public POC reduces immediate weaponization risk but does not eliminate threat from targeted attacks or future POC development. Priority should be HIGH for any WordPress installation using this plugin with untrusted contributors, MEDIUM for tightly controlled author bases.

Exploit ScenarioDerived

An attacker registers a Contributor account on a target WordPress site (or compromises existing Contributor credentials via phishing). They create or edit a Gutenberg block or classic widget and inject a malicious Display Logic expression designed to bypass the plugin's input validation by using array_map with string concatenation to construct a PHP command (e.g., system() or exec()). When the widget is rendered or the Display Logic is evaluated server-side via extras.php, the crafted expression passes through eval() and executes arbitrary PHP code with the web server's privileges, allowing the attacker to upload a web shell, exfiltrate the WordPress database including admin credentials, or pivot to the underlying server infrastructure.

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

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

Alert me

AnalysisAIv1 – May 02, 2026

Remote code execution in Widget Options plugin for WordPress (all versions ≤4.2.2) allows authenticated Contributor-level users to execute arbitrary PHP code on the server by bypassing input validation in the Display Logic feature. The plugin's unsafe use of eval() on user-controlled expressions, combined with insufficient authorization checks on the extended_widget_opts_block attribute, enables attackers to chain array_map with string concatenation to bypass blocklists. Version 4.2.0 included a partial patch, indicating the vulnerability remains exploitable in current versions. No CISA KEV listing or public POC identified at time of analysis, but EPSS data not provided for risk calibration.

RemediationAI

Upgrade Widget Options plugin to the latest version incorporating changesets 3481338 and 3514411 from the WordPress plugin repository (version number post-4.2.2, verify with WordPress.org plugin page for current stable release). The description indicates version 4.2.0 contained only a partial patch, so versions 4.2.0-4.2.2 remain vulnerable and must be upgraded. Review the specific code changes at https://plugins.trac.wordpress.org/changeset/3481338/ and https://plugins.trac.wordpress.org/changeset/3514411/ to understand the complete fix scope. As an interim compensating control if immediate patching is not feasible, restrict Contributor-level access by demoting untrusted users to Subscriber role or removing accounts entirely, though this breaks legitimate content creation workflows. Alternatively, disable the Display Logic feature entirely if the plugin provides a configuration option to do so, or temporarily deactivate the Widget Options plugin until patching is complete (side effect: all widget conditional visibility rules will stop functioning). Audit WordPress user roles using wp-admin Users panel or WP-CLI to identify all Contributor-level and above accounts, and review recent widget/block configurations for suspicious Display Logic expressions that may indicate prior exploitation attempts.

Affected VersionsENISA

Widget Options - Extended 0 ≤5.3.2
Widget Options – Advanced Conditional Visibility for Gutenberg Blocks & Classic Widgets 0 ≤4.2.2

Affected Packages

euvd widget_options_advanced_conditional_visibility_for_gutenberg_blocks_classic_widgets no fix
euvd widget_options_extended no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

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

Technical ContextAI · show details

This vulnerability affects the Widget Options plugin (also known as Widget Options Extended, identified by CPE cpe:2.3:a:marketingfire:widget_options) for WordPress. The root cause is CWE-94 (Code Injection), specifically arising from the plugin's Display Logic feature which uses PHP's eval() function to process user-supplied conditional visibility expressions. The vulnerability exists in two key files: gutenberg-toolbar.php (line 843) and extras.php (lines 495, 534) based on WordPress plugin repository references. The plugin attempts to sanitize Display Logic expressions using a blocklist/allowlist approach, but this protection can be circumvented by chaining array_map() with string concatenation techniques to construct malicious PHP code that passes validation but executes arbitrary commands when eval() processes it. The lack of proper authorization enforcement on the extended_widget_opts_block attribute allows lower-privileged users (Contributors) to supply these malicious expressions, escalating what should be a restricted administrative feature into a privilege escalation and remote code execution vector.

Know when Wordpress Plugin 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 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from Vendor (Wordfence) · only source for this CVE.

CVSS VectorVendor: Wordfence

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

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

The Widget Options WordPress plugin (versions ≤4.2.2) contains a remote code execution vulnerability affecting authenticated users with Contributor-level permissions, allowing arbitrary PHP execution on affected servers. Organizations running this plugin with contributor access grants face immediate risk of server compromise and data breach through legitimate user accounts or compromised credentials. This vulnerability requires urgent remediation as no patch is currently available from the vendor.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict Contributor role assignments to trusted users only; (2) Disable the Display Logic feature in plugin settings if available; (3) Implement WAF rules blocking POST/GET requests containing 'extended_widget_opts_block' parameter; (4) Monitor server logs for suspicious PHP eval() activity and authenticate access attempts from Contributor accounts; (5) Consider complete plugin removal if functionality is non-essential. Compensating controls do not eliminate risk and are temporary only.

Threat Intelligence Overview

EPSS Score
0.1%
Top 82% exploitable
Data Quality
6 sources
Confidence: High

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.1%
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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
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.

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

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-11749 CRITICAL POC
9.8 Nov 05

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-4295 CRITICAL POC
9.8 Jun 05

The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in

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