# CVE-2026-15236: Gallery for Google Photos < 1.2.1 - Unauthenticated Google OAuth Token Disclosure

> Unauthenticated attackers can access stored Google OAuth tokens, leading to long-term compromise of the linked Google account.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-465m-pvh5-8rh9

## What is CVE-2026-15236?

CVE-2026-15236 is a high-severity vulnerability in Unknown Gallery for Google Photos, published on 2 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Gallery for Google Photos  WordPress plugin before 1.2.1 does not properly restrict access to the stored third-party OAuth credentials of the connected account, exposing the persistent access and refresh tokens to unauthenticated users and allowing long-term compromise of the linked account.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-15236 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15236 is a high-severity vulnerability in Unknown Gallery for Google Photos, published on 2 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15236 exists.

Affected product: Unknown Gallery for Google Photos. 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-15236/ (Markdown: https://insights.sbomify.com/CVE-2026-15236/index.md)
```

## Sources

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

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