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

Harden invoice monitoring, subscription balances and API access (#7761)

Public commit record

What the developer wrote

Authored by Nicolas Dorier

58/100 · Thin
Harden invoice monitoring, subscription balances and API access (#7761)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This commit is a security hardening patch for BTCPay Server. It adds account lockout to password checks when users change their email or password, closes a JSON deserialization gap that could allow unexpected type information to be processed, limits how large Lightning payout responses can be, prevents subscription balances from growing beyond safe limits, and fixes invoice monitoring so it does not rely on stale invoice data while waiting for payments.

Recommended action

Treat this as a security hardening update and deploy promptly. Review whether any custom plugins or integrations rely on Newtonsoft.Json $type metadata deserialization, as the Ignore setting may break such flows. Monitor account lockout behavior for legitimate users entering wrong passwords.

Security signals we found

01

Account lockout now enforced on current-password verification for email and password changes

02

Newtonsoft.Json MetadataPropertyHandling.Ignore added to blob, metadata, store, and serializer settings

03

LNURL payout HTTP client response buffer capped at 256 KB

04

Subscription credit/charge bounded by GreenfieldConstants.MaxAmount in SQL, API, and UI

05

InvoiceWatcher.Wait refactored to avoid re-reading invoice entity during delayed waits

06

NBXplorer broadcast results cached and cleared on block/replacement events

07

LightningListener stores PaymentMethodId only, reducing held state

Risk score

Why this scored 61/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 8/15
Affected reach 12/15
Confidence 7/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.