# CVE-2026-10753: Site Kit by Google < 1.176.0 - Editor+ Email Reporting Settings Update

> Lower-privileged users with dashboard sharing access can modify site-wide Site Kit settings intended for administrators only.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-8rqq-v4wf-9qrm

## What is CVE-2026-10753?

CVE-2026-10753 is a low-severity missing authorization vulnerability in Unknown Site Kit by Google, published on 24 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Site Kit by Google  WordPress plugin before 1.176.0 does not properly restrict a REST API write endpoint to administrators, allowing lower-privileged users who have been granted dashboard sharing access (such as Editors) to modify a site-wide Site Kit by Google  WordPress plugin before 1.176.0 setting that should only be modifiable by administrators.

## Which versions are affected by CVE-2026-10753?


## How do I fix CVE-2026-10753?

No fix has been published for CVE-2026-10753 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10753 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10753 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10753 and fix it if it is affected.

What it is: CVE-2026-10753 is a low-severity missing authorization vulnerability in Unknown Site Kit by Google, published on 24 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10753 exists.

Affected product: Unknown Site Kit by Google. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10753/ (Markdown: https://insights.sbomify.com/CVE-2026-10753/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10753
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10753
- OSV: https://osv.dev/vulnerability/CVE-2026-10753

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10753/
Summaries are generated and may contain mistakes; the official description above is the record.