# CVE-2026-19699: GutenKit 2.4.12 - 2.4.15 - Contributor+ Mailchimp Audience Data Disclosure

> Contributors can access Mailchimp audience metadata due to insufficient capability checks in GutenKit REST API endpoints.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-hj3v-rcw6-wprx

## What is CVE-2026-19699?

CVE-2026-19699 is a low-severity missing authorization vulnerability in Unknown GutenKit, published on 20 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The GutenKit  WordPress plugin before 2.5.0 does not have a sufficient capability check on some of its REST API endpoints, allowing users with the Contributor role and above to retrieve mailing-list audience metadata from the site's connected marketing account.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-19699 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19699 is a low-severity missing authorization vulnerability in Unknown GutenKit, published on 20 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19699 in the wild and no public exploit code.

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

## Sources

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

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