CVE-2022-0313: Float Menu < 4.3.1 - Arbitrary Menu Deletion via CSRF
First published: Mon Feb 21 2022(Updated: )
The Float menu WordPress plugin before 4.3.1 does not have CSRF check in place when deleting menu, which could allow attackers to make a logged in admin delete them via a CSRF attack
Credit: contact@wpscan.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Wow-company Float Menu | <4.3.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-0313?
CVE-2022-0313 has a moderate severity due to the potential for an attacker to exploit the CSRF vulnerability to delete menu entries.
How do I fix CVE-2022-0313?
To fix CVE-2022-0313, update the Float menu WordPress plugin to version 4.3.1 or higher.
What systems are affected by CVE-2022-0313?
CVE-2022-0313 affects vulnerable versions of the Float menu WordPress plugin prior to 4.3.1.
Is authentication required to exploit CVE-2022-0313?
Yes, exploitation of CVE-2022-0313 requires the attacker to have an authenticated session with admin privileges.
What type of vulnerability is CVE-2022-0313?
CVE-2022-0313 is a Cross-Site Request Forgery (CSRF) vulnerability that can lead to unauthorized actions on behalf of a logged-in user.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/title
- agent/last-modified-date
- agent/weakness
- agent/author
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/wow-estore
- canonical/wow-company float menu