# CVE-2026-8151: Simple Membership MailChimp Integration < 1.9.8 - API Key Update via CSRF

> Attackers can trick admins into changing API keys via CSRF, redirecting member data to attacker accounts in Simple Membership MailChimp Integration.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-jj57-hm9m-766c

## What is CVE-2026-8151?

CVE-2026-8151 is a medium-severity vulnerability in Unknown Simple Membership MailChimp Integration, published on 2 Sep 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 Simple Membership MailChimp Integration WordPress plugin before 1.9.8 does not have CSRF checks in its settings page, allowing attackers to trick a logged-in administrator into changing the configured third-party API key. Once replaced, all subsequent member registration data (name, email, membership level) is sent to the attacker-controlled account.

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

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


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

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

## Is CVE-2026-8151 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8151 is a medium-severity vulnerability in Unknown Simple Membership MailChimp Integration, published on 2 Sep 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8151 exists.

Affected product: Unknown Simple Membership MailChimp Integration. 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-8151/ (Markdown: https://insights.sbomify.com/CVE-2026-8151/index.md)
```

## Sources

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

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