Easy Google Analytics for WordPress <= 1.6.0 - Cross-Site Request Forgery

Cross-Site Request Forgery (CSRF)
CVE CVE-2023-23887
CVSS 6.1 (Medium)
Publicly Published February 20, 2023
Last Updated January 22, 2024
Researcher Mika - Patchstack Alliance


The Easy Google Analytics for WordPress plugin is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.6.0. This is due to missing or incorrect nonce validation in the 'ga_admin_set.php' file. This makes it possible for unauthenticated attackers to update the plugin's Google Analytics account and client ID options to arbitrary values including a stored Cross-Site Scripting payload granted they can trick a site administrator into performing an action such as clicking on a link. Additionally the 'ga_admin_set.php' can be accessed directly, and though it is not possible to update options by doing so, loading it via a separate LFI vulnerability would allow an attacker to update options as well.



Vulnerability Details for Easy Google Analytics for WordPress

Software Type Plugin
Software Slug easy-google-analytics-for-wordpress (view on wordpress.org)
Patched? No
Remediation No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
Affected Version
  • <= 1.6.0

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.