# CVE-2026-92427: Coinsnap Bitcoin Crowdfunding <= 1.2.0 - Unauthenticated Payment Record Forgery via Webhook Secret Disclosure

> Unauthenticated attackers can disclose webhook secrets to forge payment records in the Coinsnap Bitcoin Crowdfunding WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-q2gj-9cv7-25w7

## What is CVE-2026-92427?

CVE-2026-92427 is a medium-severity vulnerability in Unknown Coinsnap Bitcoin Crowdfunding, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Coinsnap Bitcoin Crowdfunding WordPress plugin through 1.2.0 does not restrict access to the secret used to authenticate its payment gateway webhook, disclosing it to unauthenticated users and rendering the webhook's signature check ineffective. This allows unauthenticated attackers to forge payment-confirmation notifications and record arbitrary donations as completed, with attacker-chosen amounts, donor names and messages.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-92427 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92427 is a medium-severity vulnerability in Unknown Coinsnap Bitcoin Crowdfunding, published on 16 Oct 2026. 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-2026-92427 in the wild and no public exploit code.

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

## Sources

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

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