PatchSiren cyber security CVE debrief
CVE-2026-92427 Coinsnap CVE debrief
The Coinsnap Bitcoin Crowdfunding WordPress plugin through 1.2.0 discloses its payment gateway webhook secret to unauthenticated users, allowing them to forge payment-confirmation notifications and record arbitrary donations. This vulnerability enables attackers to manipulate donation records, potentially leading to financial losses and reputational damage for affected organizations. Defenders should assess exposure and prioritize verification of the plugin version and webhook secret access controls.
- Vendor
- Coinsnap
- Product
- Bitcoin Crowdfunding WordPress plugin
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-16
- Original CVE updated
- 2026-10-16
- Advisory published
- 2026-10-16
- Advisory updated
- 2026-10-16
Who should care
Defenders responsible for WordPress installations with the Coinsnap Bitcoin Crowdfunding plugin should assess exposure and prioritize verification of the plugin version and webhook secret access controls.
Why it matters
CVE-2026-92427 allows unauthenticated attackers to forge payment-confirmation notifications in the Coinsnap Bitcoin Crowdfunding WordPress plugin, enabling arbitrary donation recording.
- Unauthenticated attackers can forge payment-confirmation notifications.
- Arbitrary donations can be recorded with attacker-chosen amounts, donor names, and messages.
- Defenders need to verify plugin version and restrict access to the webhook secret.
Technical summary
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 attackers to forge payment-confirmation notifications and record arbitrary donations with attacker-chosen amounts, donor names, and messages. The vulnerability affects WordPress installations with the Coinsnap Bitcoin Crowdfunding plugin, requiring defenders to verify plugin versions and restrict access to the webhook secret.
Defensive priority
Defenders should prioritize verifying the plugin version and restricting access to the webhook secret.
Recommended defensive actions
- Verify the Coinsnap Bitcoin Crowdfunding WordPress plugin version and ensure it is up-to-date.
- Restrict access to the payment gateway webhook secret.
- Monitor for suspicious payment-confirmation notifications.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
Evidence notes
The Coinsnap Bitcoin Crowdfunding WordPress plugin through 1.2.0 does not restrict access to the secret used to authenticate its payment gateway webhook. This allows unauthenticated users to access the secret, rendering the webhook's signature check ineffective. Evidence is based on public CVE Program records and NIST NVD vulnerability assessments.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-92427 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-92427
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-92427 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-92427
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://wpscan.com/vulnerability/a5320c81-5ad9-471d-9c58-726b585b801e/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.