# CVE-2026-7520: Missing authorization in Mailmunch Forms for Mailchimp

> Authenticated subscribers can hijack MailMunch integration to steal subscriber data and control site forms due to missing capability checks.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-49m8-524g-8rr2

## What is CVE-2026-7520?

CVE-2026-7520 is a high-severity missing authorization vulnerability in Mailmunch Forms for Mailchimp, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The MailChimp Forms by MailMunch plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `sign_in()` and `sign_up()` AJAX handlers in all versions up to, and including, 3.2.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to relink the site's MailMunch integration to an attacker-controlled MailMunch account by submitting attacker-supplied credentials. Once relinked, all subscriber data captured by the plugin's forms is delivered to the attacker, and the forms/landing pages rendered on the site are pulled from the attacker's MailMunch account.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-7520 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7520 is a high-severity missing authorization vulnerability in Mailmunch Forms for Mailchimp, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7520 in the wild and no public exploit code.

Affected product: Mailmunch Forms for Mailchimp. 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-7520/ (Markdown: https://insights.sbomify.com/CVE-2026-7520/index.md)
```

## Sources

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

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