AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
High 78 Bitcoin

Harden account and payment handling

Public commit record

What the developer wrote

Authored by Andrew Camilleri (Kukks)

45/100 · Thin
Harden account and payment handling
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This is a large hardening patch for BTCPay Server that fixes several security weaknesses around account handling, payments, refunds, and plugins. Key changes include: preventing Blazor circuits from staying authenticated after a user's admin rights or account status changes; stopping users from creating multiple simultaneous refunds for the same invoice; requiring extra permission when a payout approval specifies a custom exchange rate; preventing hot-wallet flags from being silently carried over to a different wallet; adding rate limits to anonymous monetization signups and LNURL invoice generation; fixing PayJoin transaction locking so funds are not accidentally double-spent; and making plugin dependency downloads safer against cycles and partial installs. The commit message and code comments frame these as hardening measures rather than a single critical vulnerability.

Recommended action

Treat this as a security hardening release and deploy promptly. Review the listed components for any custom forks or local patches that may conflict with the new revalidation, refund serialization, payout approval, hot-wallet, or PayJoin behavior. Run the included tests, especially CircuitUserRevalidatorTests, GreenfieldAPITests, PayJoinTests, PluginManagerTests, and RateAccountingSecurityTests, before production deployment. No CVE or advisory is supplied, so monitor BTCPay Server release notes for formal disclosure details.

Security signals we found

01

Blazor circuit principal revalidation against live user state

02

Cookie principal rejection when user is administratively restricted

03

Refund creation serialized with SELECT FOR UPDATE and single open refund enforcement

04

Payout approval with explicit RateRule gated by CanCreatePullPayments

05

Hot-wallet flag no longer transferable to a different derivation scheme

06

HighSpeed speed policy normalized to MediumSpeed, removing zero-confirmation handling

07

Rate limiting added to anonymous monetization signup and LNURL invoice generation

08

PayJoin UTXO locking and delayed-broadcast cleanup to prevent double-spend/lock leaks

09

Plugin dependency resolution hardened against cycles and partial installs

010

On-chain automated payout claims and reversion on broadcast failure

Risk score

Why this scored 78/100

Our methodology →
Potential impact 24/30
Exploitability 18/25
Stealth signal 10/15
Affected reach 14/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.