BTCPay Server 2.4.7: bug-fix release addresses 85 security findings; update especially recommended for shared servers

The vendor has released 2.4.7 and describes it as a bug-fix release addressing security, reliability and payment accounting issues; the scan report lists 85 findings fixed (1 Critical, 13 High, 52 Medium, 19 Low), with details of Critical and High findings deliberately withheld. The named fixes include: canceled payouts can no longer be reopened to bypass pull payment limits; confirmation policies and expiry limits apply to anonymously created BitPay API invoices, reading an individual invoice requires authentication, and supplied tokens are checked against the authenticated identity; cases where forms, search, notifications and Greenfield listings exposed another store's data or forms have been fixed; 2FA attempt limits have been strengthened for concurrent logins; LNURL-auth challenges expire after five minutes and are invalidated when credentials change; cached addresses are checked for ownership by the current wallet after replacement, deletion or multisig setup. The vendor strongly recommends the update, particularly for servers shared by several merchants. The legacy /invoices/create routes have also been removed in favor of /stores/{storeId}/invoices/create.