# CVE-2026-92433: Patreon WordPress < 1.10.0 - Patreon Integration Takeover via CSRF

> Attackers can hijack Patreon integration via CSRF, allowing unauthorized account linking and potential data exposure for WordPress site administrators.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-w3q2-34vh-jqmw

## What is CVE-2026-92433?

CVE-2026-92433 is a medium-severity vulnerability in Unknown Patreon WordPress, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Patreon WordPress plugin before 1.10.0 does not verify a nonce when connecting the site to a Patreon account, allowing attackers to make a logged-in administrator re-link the integration to an attacker-controlled account via a crafted request (CSRF), taking over the site's Patreon integration.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-92433 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92433 is a medium-severity vulnerability in Unknown Patreon WordPress, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92433 in the wild and no public exploit code.

Affected product: Unknown Patreon WordPress. 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-92433/ (Markdown: https://insights.sbomify.com/CVE-2026-92433/index.md)
```

## Sources

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

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