Different Menu in Different Pages – Control Menu Visibility (All in One) <= 2.3.2 - Missing Authorization to Menu Duplication
Strategic Overview
- Status
- Patched in 2.4.0
- Affected Plugin
- Different Menu in Different Pages – Conditional Menu
- Affected Version
<= 2.3.2- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-3206
At a glance
CVE-2024-3206 is a medium-severity Missing Authorization vulnerability in the Different Menu in Different Pages WordPress plugin, affecting versions <= 2.3.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.4.0; sites on affected versions should update now. Disclosed April 2024, reported by Lucio Sá.
Vulnerability Overview
The Different Menu in Different Pages – Control Menu Visibility (All in One) plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the ajax() function in all versions up to, and including, 2.3.2. This makes it possible for authenticated attackers, with subscriber-level access and above, to duplicate menus.
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-862: Missing Authorization
Different Menu in Different Pages <= 2.3.2 carries this weakness at ajax(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Different Menu in Different Pages the fix is 2.4.0: builds <= 2.3.2 are affected, anything from 2.4.0 onward is not.
Remediation
Update to version 2.4.0, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Different Menu in Different Pages 2.4.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C