# CVE-2024-37430: WordPress Patreon WordPress plugin <= 1.9.0 - Image Protection Bypass vulnerability

> An authentication bypass vulnerability in the Patreon WordPress plugin allows attackers to bypass image protection mechanisms via spoofing.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 9 Jul 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-p8vv-x9fq-f9hx

## What is CVE-2024-37430?

CVE-2024-37430 is a medium-severity authentication bypass vulnerability in Patreon WordPress, published on 9 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication Bypass by Spoofing vulnerability in patreon Patreon WordPress patreon-connect.This issue affects Patreon WordPress: from n/a through <= 1.9.0.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2024-37430?


## How do I fix CVE-2024-37430?

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

## Is CVE-2024-37430 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37430 and fix it if it is affected.

What it is: CVE-2024-37430 is a medium-severity authentication bypass vulnerability in Patreon WordPress, published on 9 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-37430 in the wild and no public exploit code.

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

## Sources

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

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