# CVE-2026-119564: Plausible Analytics through 3.2.1 Site Takeover via Exposed Invitation IDs


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-2p4r-4pmj-4wp8

## What is CVE-2026-119564?

CVE-2026-119564 is a medium-severity vulnerability in Plausible Analytics, published on 30 Oct 2026. 

### Official description

Plausible Analytics Community Edition through 3.2.1 contains an information exposure vulnerability that allows site editors to obtain pending invitation and ownership-transfer IDs from the settings/people page. Attackers can register with the invitee's email using the exposed ID and accept it, gaining the invited role or taking site ownership.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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


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

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

## Is CVE-2026-119564 being exploited?

There is no known exploitation of CVE-2026-119564 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119564 is a medium-severity vulnerability in Plausible Analytics, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119564 in the wild and no public exploit code.

Affected product: Plausible Analytics. 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-119564/ (Markdown: https://insights.sbomify.com/CVE-2026-119564/index.md)
```

## Sources

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

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