HomeWordPress vulnerabilitiesWidget Options
Widget Options vulnerabilities
Widget Options has 4 known vulnerabilities in this database. The most recent published record is dated 13 Nov 2026.
- Known vulnerabilities
- 4
- Active installs
- 100,000+
- Latest version
- 4.2.6.1
- Last updated
- 26 Oct 2026
- Most recent
- 13 Nov 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2026-116615 | High 8.8 | Up to 4.2.6.1 | No fixed version yet | 9 d ago |
| Remote code execution CVE-2026-116852 | Critical 9.1 | Up to 4.2.5 | Fixed in a later version (latest 4.2.6.1) | 30 Oct 2026 |
| Remote code execution CVE-2026-2052 | High 8.8 | Up to 4.2.2 | Fixed in a later version (latest 4.2.6.1) | 2 May 2026 |
| Remote code execution CVE-2024-8672 | Critical 9.9 | Up to 4.0.7 | Fixed in a later version (latest 4.2.6.1) | 28 Nov 2024 |
Read the published descriptions
- CVE-2026-116615, 13 Nov 2026
- The Widget Options - Advanced Conditional Visibility for Gutenberg Blocks & Classic Widgets plugin for WordPress is vulnerable to Code Injection in all versions up to, and including, 4.2.6.1 via the `post_content` parameter. This is due to asymmetric parsing between the save-time strip filter (`widgetopts_strip_logic_from_blocks()`) and the render-time parser (`blockopts_filter_before_display()`): embedding an inner `<!--start_widgetopts` literal inside a JSON key causes the write-side `json_decode` to see a non-`class` key and skip stripping - persisting the payload verbatim to the database - while the render-side `str_replace` reconstitutes the key to `class`, feeding the attacker-controlled `logic` value directly into `@eval`. This makes it possible for authenticated attackers, with Author-level access and above, to inject PHP expressions that execute on every front-end page view, enabling boolean-oracle exfiltration of WordPress site configuration data - including admin email address, default role, and arbitrary `get_option`, `get_user_meta`, and `get_post_meta` values - via the plugin's allowlisted-function sandbox, which escalates to unrestricted code execution if any installed plugin extends the `widgetopts_allowed_php_functions` filter. Contributors can also exploit this vulnerability when their submitted post is later published by an administrator; notably, the injected payload executes for all site visitors, including unauthenticated users, because a trust-flag mechanism introduced in version 4.2.6 causes `widgetopts_safe_eval_trusted()` to bypass its non-admin short-circuit at every legacy render callsite. Exploitation by attackers with contributor-level access and above requires that an administrator (or editor) later publishes the contributor's submission. On a default installation, where that is not configured, the vulnerability requires attackers with author-level access and above. CVE record
- CVE-2026-116852, 30 Oct 2026
- Author Remote Code Execution (RCE) in Widget Options <= 4.2.5 versions. CVE record
- CVE-2026-2052, 2 May 2026
- 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. CVE record
- CVE-2024-8672, 28 Nov 2024
- The Widget Options - The #1 WordPress Widget & Block Control Plugin plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.0.7 via the display logic functionality that extends several page builders. This is due to the plugin allowing users to supply input that will be passed through eval() without any filtering or capability checks. This makes it possible for authenticated attackers, with contributor-level access and above, to execute code on the server. Special note: We suggested the vendor implement an allowlist of functions and limit the ability to execute commands to just administrators, however, they did not take our advice. We are considering this patched, however, we believe it could still be further hardened and there may be residual risk with how the issue is currently patched. CVE record
What to do if you run Widget Options
If you run Widget Options, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Widget Options vulnerabilities
Free. We email you when a new vulnerability is published for Widget Options, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.