CVE-2024-35691

Widget Options - Extended <= 5.1.0 & Widget Options <= 4.0.1 - Authenticated (Subscriber+) Information Disclosure

2024-06-06 00:00
Dave Jong

Strategic Overview

Status
Patched in 4.0.2
Affected Version
<= 4.0.1
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-35691
View all Widget Options – Advanced Conditional Visibility for Gutenberg Blocks & Classic Widgets vulnerabilities

At a glance

CVE-2024-35691 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Widget Options WordPress plugin, affecting versions <= 4.0.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.0.2; sites on affected versions should update now. Disclosed June 2024, reported by Dave Jong.

Vulnerability Overview

The Widget Options - Extended plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to 5.1.3 (exclusive) for Widget Options - Extended and all versions up to, and including, 4.0.1 for Widget Options. This makes it possible for unauthenticated attackers to extract sensitive data including private/draft posts and user meta. CVE-2024-35690 was also assigned to this issue (specifically for the free version)

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Widget Options <= 4.0.1 takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Widget Options the fix is 4.0.2: builds <= 4.0.1 are affected, anything from 4.0.2 onward is not.

Remediation

Update to version 4.0.2, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Widget Options 4.0.2 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C