WP Mobile Menu <= 2.8.4.4 - Missing Authorization to _mobmenu_icon Post Meta Modification
Strategic Overview
- Status
- Patched in 2.8.5
- Affected Plugin
- WP Mobile Menu – The Mobile-Friendly Responsive Menu
- Affected Version
<= 2.8.4.4- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-2508
At a glance
CVE-2024-2508 is a medium-severity Missing Authorization vulnerability in the WP Mobile Menu WordPress plugin, affecting versions <= 2.8.4.4. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.8.5; sites on affected versions should update now. Disclosed July 2024, reported by 1337_Wannabe.
Vulnerability Overview
The WP Mobile Menu plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the save_menu_item_icon function in all versions up to, and including, 2.8.4.4. This makes it possible for unauthenticated attackers to add the '_mobmenu_icon' post meta to arbitrary posts with an arbitrary (but sanitized) value. NOTE: Version 2.8.4.4 contains a partial fix for this vulnerability.
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 privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
WP Mobile Menu <= 2.8.4.4 carries this weakness at _mobmenu_icon, 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 WP Mobile Menu the fix is 2.8.5: builds <= 2.8.4.4 are affected, anything from 2.8.5 onward is not.
Remediation
Update to version 2.8.5, 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: WP Mobile Menu 2.8.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Mobile Menu – The Mobile-Friendly Responsive Menu
- 6.1CVE-2024-13362: Freemius <= 2.10.1 Reflected DOM-Based XSS
CVE-2024-13362 - 6.1CVE-2023-33999: Freemius SDK <= 2.5.9 Reflected Cross-Site Scripting
CVE-2023-33999 - 6.1CVE-2021-24435: Titan Framework <= (Various Versions) Reflected XSS
CVE-2021-24435 - 5.4CVE-2024-3987: WP Mobile Menu Stored XSS
CVE-2024-3987 - 4.3CVE-2024-37274: WP Mobile Menu <= 2.8.4.3 Cross-Site Request Forgery
CVE-2024-37274
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C