Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

google/site-kit-wp

              develop @ 4697d87
            

Fixes

CVEs

HIGH

Peak severity

30.0%

Coverage

Highlights

Auth Bypass: 44 prior fixes. Scrutinize any change in this area.

includes/Core/Permissions/Permissions.php: most-fixed (14 issues). Treat as high-risk during review.

22 high-severity fixes in this history; regressions here are high-impact.

Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Auth Bypass: The plugin relies on complex capability mappings for its dashboard sharing and user permissions. Historically, logical flaws such as checking permissions under the wrong user context, missing setup-completion gates, or failing to enforce administrative capabilities have repeatedly led to privilege escalation and authorization bypasses.

SSRF: SSRF vulnerabilities occurred due to parsing discrepancies where pre-parsed hostnames were sent to request blockers instead of raw URIs, or because third-party clients (Guzzle HTTP) did not inherit standard WordPress host-blocking rules.

Auth Bypass: The integration of Sign in with Google introduced critical logic flows that bypassed standard WordPress registration and profile linking protections, occasionally missing proper CSRF validations or failing to restrict actions to administrative domains.