Site Kit by Google vulnerability history, Google connections and dashboard sharing
Site Kit ties WordPress to Google services through each administrator's own Google account, places Google tags on public pages and can share a view-only dashboard with other roles.
Read those connections as well as the installed version.
On this page
Site Kit by Google vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 3 records for Site Kit by Google. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 1.187.0
Worked out from data retrieved on .
Every affected range listed in this source for Site Kit by Google ends before version 1.187.0.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
Site Kit by Google - Analytics, Search Console, AdSense, Speed <= 1.186.0 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2026-62139
Affected versions- All versions up to and including 1.186.0
Patched versions: 1.187.0
Update to at least version 1.187.0.
Site Kit by Google - Analytics, Search Console, AdSense, Speed < 1.176.0 - Missing Authorization to Authenticated (Editor+) Settings Update
- Published:
- Last updated:
- Severity:
- Low (CVSS 2.7)
- CVE:
- CVE-2026-10753
Affected versions- All versions before 1.176.0
Patched versions: 1.176.0
Update to at least version 1.176.0.
Site Kit by Google <= 1.7.1 - Sensitive Information Disclosure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2020-8934
Affected versions- All versions up to and including 1.7.1
Patched versions: 1.8.0
Update to at least version 1.8.0.
Check Site Kit by Google on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What Site Kit by Google connects, and where it takes input
Site Kit by Google is published on WordPress.org by Google, and the listing calls it the official WordPress plugin from Google for insights about how people find and use your site.
It lists Search Console, Analytics, AdSense, PageSpeed Insights, Tag Manager, Sign in with Google, Reader Revenue Manager and Ads, and says that where a site has multiple WordPress admins, each admin must connect their own Google account in order to access the plugin.
Only users with the Administrator role can set up Site Kit, configure settings and connect services, according to its permissions page. Google's dashboard sharing guide says roles that include the edit_posts capability can be given a restricted, view-only dashboard. Visitors give it input through Sign in with Google, which its guide says puts a login button on standard WordPress login pages, including WooCommerce login pages, and whose settings can add a One Tap prompt and a button next to comments.
Reading the Site Kit records by their version fields
The history on this page lists the records the source data files under the slug google-site-kit.
The title of CVE-2020-8934 names the plugin "Site Kit by Google" alone, while CVE-2026-62139 and CVE-2026-10753 add "Analytics, Search Console, AdSense, Speed", so match on the version fields rather than the name.
CVE-2026-62139 has a title ending "Cross-Site Request Forgery". It affects all versions up to and including 1.186.0, and its patched versions field lists 1.187.0. CVE-2026-10753 has a title ending "Authenticated (Editor+) Settings Update", the only one of the three named here to name a WordPress role. It affects all versions before 1.176.0, with 1.176.0 patched.
CVE-2020-8934 has a title ending "Sensitive Information Disclosure". Its affected range runs up to and including 1.7.1, and its patched versions field lists 1.8.0. The fields say nothing about the versions between the two, so for that record the patched version is the one to reach. With each affected range and patched versions field matched, read the update guidance at the top of the history.
The listing also links to a changelog for all versions, where some entries carry the line "This release includes security fixes. An update is strongly recommended."
Where each Site Kit setting is read on a site you may review
Google's settings page puts Site Kit's settings at Site Kit > Settings, in the tabs Connected Services, Connect More Services and Admin Settings.
Read them and change nothing. Leave Edit, Disconnect and Reset Site Kit alone. The same page says a reset deletes all code snippets Site Kit placed on your site and any preferences you set in Site Kit.
On the Plugins screen, the Description column gives the installed version and the Update Available link lists plugins with an upgrade available at the WordPress Plugin Directory. Record the action link the Automatic update column shows for the plugin.
The Connected Services tab shows every Google service connected through Site Kit, and the down arrow on each expands its details. Record each service and its details without pressing Edit. Google's guide to connecting services calls Search Console a required service, and the permissions page says it cannot be disconnected within Site Kit because it is used to verify site ownership. The same guide says PageSpeed Insights is enabled by default and adds no code to your site.
Google's dashboard sharing guide calls the administrator who connected a service with their Google account the "owner" of that connection, and the permissions page says setup grants Owner permissions in Search Console through that account. Record which administrators have connected an account and which services each one owns.
In the Google account menu, opened from the profile photo or initial at the top right of the Site Kit dashboard, leave Disconnect alone. Google says it removes your user's access to all services.
For Sign in with Google, read Site Kit > Settings > Connected Services > Sign in with Google. Its guide says the Client ID there identifies the Google Cloud project Site Kit helps create, through a setup step with a Get OAuth Credentials button.
Record whether a Client ID is set, the state of "Enable One Tap sign in", "One-Tap enabled on all pages" and "Show next to comments", and the User registration status, which the guide links to the Anyone can register checkbox in Settings > General.
The sharing icon in the Site Kit header opens the dashboard sharing settings, which Google's guide says are available only to an administrator who has signed in to Site Kit with their own Google account. For each service in the table, drawn from AdSense, Analytics, PageSpeed Insights and Search Console, record the roles under "Who can view" and the value of "Who can manage view access".
The guide says that setting appears only on sites with more than one administrator and defaults to "Only me", while PageSpeed Insights is always set to "Any admin signed in with Google". Read the table without the Edit roles icon, Apply or the Reset sharing permissions link.
The guide says users keep access to shared data unless an administrator alters the permissions. Compare the roles you recorded with the Role column on the Users screen.
Google's page on the Google tag says that once Analytics is set up, Site Kit > Settings > Connected Services > Analytics shows the GA4 measurement ID and the Google tag ID, and that the tag can be verified by searching the website's source code for that ID, which has a "GT-" prefix.
Record both IDs, then note every Google tag, Tag Manager container and AdSense snippet in a public page's source.
Not every tag there comes from Site Kit. Google's page on Site Kit-placed code lists other places to check, including theme settings, the header.php and footer.php templates, Tag Manager containers and plugins that insert header or footer scripts. It says keeping an existing GA4 tag while Site Kit inserts one for another property tracks data to both properties.
What a Site Kit version match cannot read
A version match shows whether the installed release falls inside a known record's affected range.
It cannot show whether a flaw was used, whose Google account owns each connection, which roles see the view-only dashboard, whether One Tap shows on every page, or whether a theme template prints a second Analytics tag.
Two WordPress security audit tests fit Site Kit. The audit confirms that editors cannot reach plugin, theme, user or settings requests by calling them directly. Where Anyone can register is ticked, which Sign in with Google needs for new sign-ups, it also confirms that a new sign-up lands in the default role you chose and cannot pick a higher one.
Frequently asked questions
Through Sign in with Google, but only if the WordPress setting Anyone can register is enabled, Site Kit's guide says. The role a new user receives comes from the WordPress general settings, with Subscriber the default, which can be changed. WordPress's Settings General page lists Administrator among the choices for the New User Default Role. Read that setting beside the Sign in with Google User registration status.
Site Kit's permissions page says that when an administrator sets it up, Site Kit grants Owner permissions in Search Console using their own Google account and verifies site ownership unless it is already verified. A later administrator who sets it up and is not yet a verified owner is verified during setup as well, also gaining Owner permissions.
Google's dashboard sharing guide says that if a shared module's owner is deleted from the site, disconnected from Site Kit or has their role changed from admin, another administrator with access can recover the module from the "Dashboard data for some services has been interrupted" banner and becomes its owner. Where the owner disconnected their Google account, non-administrators see a placeholder until the module is recovered. Note whether that banner shows, without pressing Recover.
It depends on the services connected. Google's guide to connecting services says Site Kit adds Tag Manager code snippets to the head and body by default, can insert the AdSense code snippet, and places the Ads code snippet when Ads is connected, while PageSpeed Insights adds no code. Where it finds existing code for Analytics, Tag Manager or AdSense during setup, its page on placed code says it lets you choose whether Site Kit places its own snippet instead.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to every record listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- Site Kit by Google - Analytics, Search Console, AdSense, Speed <= 1.186.0 - Cross-Site Request Forgery (CVE-2026-62139)
- Site Kit by Google - Analytics, Search Console, AdSense, Speed < 1.176.0 - Missing Authorization to Authenticated (Editor+) Settings Update (CVE-2026-10753)
- Site Kit by Google <= 1.7.1 - Sensitive Information Disclosure (CVE-2020-8934)