Takanakui WP Mobile Menu – The Mobile Friendly Responsive Menu vulnerabilities

4 vulnerabilities

Known vulnerabilities in Takanakui WP Mobile Menu – The Mobile Friendly Responsive Menu, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

6.3CVE-2022-49745starpluginseasy_age_verify+1239
EPSS score
0.44%
The Freemius SDK, as used by hundreds of WordPress plugin and theme developers, was vulnerable to Cross-Site Request Forgery and Information disclosure due to missing capability checks and nonce protection on the _get_debug_log, _get_db_option, and the _set_db_option functions in versions up to, and including 2.4.2. Any WordPress plugin or theme running a version of Freemius less than 2.4.3 is vulnerable.5.3CVE-2024-2508takanakuiwp mobile menu – the mobile-friendly responsive menu+1
EPSS score
0.36%
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.6.1CVE-2024-13362100pluginsopen_user_map+262
EPSS score
0.28%
Multiple plugins and/or themes for WordPress are vulnerable to Reflected Cross-Site Scripting via the url parameter in various versions due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.5.4CVE-2024-3987freshlightlabwp_mobile_menu+2
EPSS score
0.27%
The WP Mobile Menu – The Mobile-Friendly Responsive Menu plugin for WordPress is vulnerable to Stored Cross-Site Scripting via image alt text in all versions up to, and including, 2.8.4.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.