CVE-2022-44587: WordPress WP 2FA plugin <= 2.6.3 - Sensitive Data Exposure via Log File vulnerability
First published: Fri Jun 21 2024(Updated: )
Insertion of Sensitive Information into Log File vulnerability in WP 2FA allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WP 2FA: from n/a through 2.6.3.
Credit: audit@patchstack.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Melapress WP 2FA | <2.6.4 |
Remedy
Update to 2.6.4 or a higher version.
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.
Frequently Asked Questions
What is the severity of CVE-2022-44587?
CVE-2022-44587 is classified as a medium severity vulnerability.
How do I fix CVE-2022-44587?
To fix CVE-2022-44587, upgrade the WP 2FA plugin to version 2.6.4 or higher.
What systems are affected by CVE-2022-44587?
CVE-2022-44587 affects WP 2FA versions up to 2.6.3.
What type of vulnerability is CVE-2022-44587?
CVE-2022-44587 is an Insertion of Sensitive Information into Log File vulnerability.
What can attackers do with CVE-2022-44587?
Attackers can access functionality not properly constrained by ACLs due to CVE-2022-44587.
- agent/remedy
- agent/title
- agent/weakness
- agent/references
- agent/description
- agent/type
- agent/first-publish-date
- agent/author
- agent/event
- agent/severity
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/melapress
- canonical/melapress wp 2fa