CVE-2022-38137: WordPress Analytify plugin <= 4.2.2 - Cross-Site Request Forgery (CSRF) vulnerability
First published: Tue Nov 08 2022(Updated: )
Cross-Site Request Forgery (CSRF) vulnerability in Analytify plugin <= 4.2.2 on WordPress.
Credit: audit@patchstack.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Analytify - Google Analytics Dashboard | <4.2.3 |
Remedy
Update to 4.2.3 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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-38137?
CVE-2022-38137 is classified as a high severity Cross-Site Request Forgery (CSRF) vulnerability.
How do I fix CVE-2022-38137?
To fix CVE-2022-38137, update the Analytify plugin to version 4.2.3 or later.
What are the potential impacts of CVE-2022-38137?
CVE-2022-38137 could allow attackers to perform unauthorized actions on behalf of users, potentially compromising user accounts.
Is my WordPress site affected by CVE-2022-38137?
If you are using Analytify plugin version 4.2.2 or earlier, your WordPress site is affected by CVE-2022-38137.
What is the nature of CVE-2022-38137?
CVE-2022-38137 is a Cross-Site Request Forgery vulnerability that allows unauthorized actions through a malicious request.
- agent/references
- agent/type
- agent/author
- agent/weakness
- agent/softwarecombine
- agent/description
- agent/severity
- agent/title
- agent/remedy
- agent/source
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/analytify
- canonical/analytify - google analytics dashboard