WordPress Site Kit by Google plugin <= 1.186.0 - Cross Site Request Forgery (CSRF) vulnerability

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Google/Site Kit by Google (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Google/Site Kit by Google.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 11, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 11, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 11, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• WordPress RTMKit plugin <= 2.1.5 - Cross Site Request Forgery (CSRF) vulnerabilityAlso CWE-352
• Improper Restriction of XML External Entity References in AWS Advanced JDBC Wrapper RemoteQueryCachePluginSame generic ecosystem
• Concrete CMS 9.2.0 to 9.5.2 Express REST API list endpoint exposes restricted Express entries via Missing AuthorizationSame generic ecosystem
• WordPress Deposits and Partial Payments for WooCommerce plugin <= 3.1.0 - Broken Access Control vulnerabilitySame generic ecosystem
• Laci Synchroni Backend Vulnerable to Account Takeover / User Impersonation via Client-Side Configuration ManipulationSame generic ecosystem
• Authorizer: Unvalidated redirect_uri in /authorize leaks OAuth2 tokens to attacker-controlled URLSame generic ecosystem