← WordPress Vulnerabilities
WordPress security by component

Analyticator

Analyticator is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Jan 23, 2023; the highest CVE/CNA score is 8.8.

Plugin slug: google-analyticator

CVE-2022-4323: Analyticator: Code execution

Analyticator is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

PublishedJan 23, 2023
Safe version guidanceSee mitigation notes
Safe version
Jan 23, 2023 CVE-2022-4323
Analyticator: Code execution
Analyticator is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.
See mitigation notes
CVE7.2
NVD7.2
Jan 23, 2023 CVE-2022-3425
Analyticator: Code execution
Analyticator is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.
See mitigation notes
CVE7.2
NVD7.2
Aug 22, 2019 CVE-2009-5158
Google Analyticator: A security weakness
Google Analyticator is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE6.1
NVD6.1
Sep 07, 2017 CVE-2015-4697
Google Analyticator: Cross-site request forgery
Google Analyticator is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
See mitigation notes
CVE8.8
NVD8.8
Sep 21, 2015 CVE-2015-6238
Google Analyticator: Cross-site scripting
Google Analyticator is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE4.3
NVD4.3