# CVE-2026-6709: Missing authorization in Coinbase Commerce for Contact Form 7

> Authenticated subscribers can modify the Coinbase Commerce API key due to missing authorization checks in the plugin settings.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 12 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-w945-6648-pwv3

## What is CVE-2026-6709?

CVE-2026-6709 is a medium-severity missing authorization vulnerability in coderpress Coinbase Commerce for Contact Form 7, published on 12 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Coinbase Commerce for Contact Form 7 plugin for WordPress is vulnerable to Missing Authorization in versions up to and including 1.1.2. This is due to a missing capability check and missing nonce verification in the save_settings() function, which is registered on the admin_post_cccf7_save_settings hook. This makes it possible for authenticated attackers, with Subscriber-level access and above, to overwrite the plugin's Coinbase Commerce API key option (cccf7_api_key) via a crafted POST request to /wp-admin/admin-post.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-6709 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6709 is a medium-severity missing authorization vulnerability in coderpress Coinbase Commerce for Contact Form 7, published on 12 May 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-6709 in the wild and no public exploit code.

Affected product: coderpress Coinbase Commerce for Contact Form 7. 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-6709/ (Markdown: https://insights.sbomify.com/CVE-2026-6709/index.md)
```

## Sources

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

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