Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
53/100 average clarity
90Strong · 80–100
213Adequate · 60–79
480Thin · 40–59
194Opaque · 0–39
10security candidates with opaque commit messaging
This commit is a simple rename of a code attribute from UseStoreLanguageAttribute to StorefrontRouteAttribute. It only changes the name used in source files and does not alter any program behavior, security settings, or access controls.
This commit changes how the invoice checkout page is translated. Instead of loading translations from separate JSON files in the browser based on a language the customer picks, the page now uses the store's own server-side translation sett…
Removal of client-side language selection reduces attack surface for language-related query-string manipulation (e.g., lang=...)Server-side rendering of checkout strings may reduce exposure to DOM-based XSS via translation files, but no specific vulnerability is shownLarge deletion of locale files and i18next vendor scripts is a cleanup, not a patch
This commit updates two .NET runtime/SDK Docker images to newer patch versions and bumps a third-party library (CsvHelper) from 34.0.0 to 34.1.0. These are routine maintenance updates. The commit message does not say any of the updates fix…
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 adm…
Blazor circuit principal revalidation against live user stateCookie principal rejection when user is administratively restrictedRefund creation serialized with SELECT FOR UPDATE and single open refund enforcement
20ae3337by Andrew Camilleri (Kukks)+1310−41655 files
This commit removes a per-invoice checkout language option and translates more public-facing text so it can be localized. It is a feature-cleanup and internationalization change, not a security fix. There is no evidence of a vulnerability …
This commit fixes a bug where BTCPay Server's Point of Sale and Crowdfund inventory counts could become wrong after unpaid or expired invoices. Previously, the system could add inventory back multiple times for the same invoice, making it …
Business-logic flaw: inventory counts could be inflated by duplicate restocking eventsState-machine fix: previous status now tracked to prevent double-countingRace/ordering concern mitigated by deterministic event-barrier for tests
This commit fixes a bug in BTCPay Server where marking an already-expired invoice as 'invalid' could cause the app inventory to be restocked twice. The fix tracks each invoice's previous status during status transitions and skips the inven…
Business-logic bug causing duplicate inventory restockingStatus-transition event missing prior-state contextInventory manipulation possible through invoice state changes
This commit adds a new store-level setting that lets merchants choose which language customers see on public pages such as invoices, payment requests, and pull payments. It also marks more text on those pages as translatable. There is no d…
New per-request language scoping via AsyncLocal with explicit BeginRequest/Restore disposalSignalR hub now applies store language to controller calls that bypass MVC filtersRouteStoreResolver centralizes route-value-to-store-id lookup with 10-minute sliding memory-cache
This commit fixes two bugs in BTCPay Server's wallet transaction API. First, when users filtered transactions by both status (confirmed/unconfirmed) and label, the same transaction could appear twice in the results because the filtering lo…
Fixes duplicate entries in API query results due to incorrect filter compositionReplaces unsafe uint256.Parse with uint256.TryParse to prevent unhandled exceptions on malformed inputAdds server-side input validation returning structured 404 API error for invalid transaction IDs
This commit only updates the version tag of the LND (Lightning Network Daemon) Docker image used in test environments from v0.21.7-beta to v0.21.8-beta. It does not change any production application code, configuration logic, or runtime be…
This commit simply bumps the version numbers of three NuGet packages: a test reporting helper and two FIDO2 authentication libraries. There is no indication in the commit itself that these updates fix a security problem, and no external re…
This commit updates many third-party software libraries (NuGet packages) to newer versions and makes small code adjustments so BTCPay Server stays compatible with those updates. The most notable security-relevant change is a rewrite of the…
Dependency version bumps for libraries with known security maintenance value (HtmlSanitizer, Fido2, MailKit, Microsoft.AspNetCore, System.Security.Cryptography.Pkcs)Manual CSV field escaping added to prevent formula/CSV injection in wallet transaction exportsFido2 configuration/AppID handling changed during Fido2 library upgrade
This commit fixes a crash in BTCPay Server's admin page that shows how an API key has been used. The crash happened when an API key had permissions tied to more than one store. The fix also corrects how usage counts are recorded and displa…
Fixes a UI crash in an administrative API-key usage pageCorrects aggregation of permission usage records when permissions are scoped to specific storesChanges database upsert to persist full permission string including store scope
This commit fixes a crash in BTCPay Server's admin page that shows how an API key has been used. The crash happened when the same permission (like 'view invoices') was used for more than one store. The fix also corrects how usage counts ar…
Fixes a runtime crash in an administrative API-key usage viewCorrects aggregation of permission usage records that previously could duplicate or conflate store-scoped entriesChanges upsert to persist full permission string including scope, preventing legacy-style policy-only rows from overwriting each other
This commit fixes a math bug in how BTCPay Server rounds very small negative amounts. Previously, a helper called RoundToSignificant divided by the signed value instead of its absolute value, so negative numbers behaved differently from po…
Rounding/truncation bug in financial amount handlingNegative-amount handling asymmetry that could alter displayed or computed balancesFee-bump calculation could fall below Bitcoin incremental relay fee requirement
This commit fixes a crash in the API key authorization page. When a user submits the form without clicking either the 'Authorize' or 'Cancel' button, the server tries to read a missing command value, which could cause an error. The fix saf…
Null dereference in request handling pathUnhandled exception could lead to error disclosure or availability impactDefensive null-safety hardening in controller action
This commit hardens how BTCPay Server downloads translation files from GitHub. It adds checks so the app only fetches files from the project's own trusted GitHub organization, blocks automatic web redirects, and supports a new optional red…
Server-side request forgery (SSRF) protection added: URI host/path validation before outbound fetchAutomatic HTTP redirects disabled for translation update clientManifest redirect field introduced with same-origin/org trust validation
This commit hardens how BTCPay Server downloads translation files from the internet. It adds checks so the server only fetches language packs and manifest redirects from the trusted btcpayserver GitHub organization, turns off automatic HTT…
Server-side request forgery (SSRF) hardening: URI scheme, host, and path prefix are validated before outbound fetchOpen-redirect / HTTP redirect abuse mitigation: AllowAutoRedirect set to false on the translation HttpClientPath traversal mitigation: pack file paths resolved as relative URIs and validated against trusted org prefix
This commit removes old database upgrade scripts (migrations) from before BTCPay Server version 1.12.0 and replaces them with a single consolidated starting schema. It also trims the startup migration task by deleting obsolete data-convers…
Large-scale deletion of database migration historyConsolidation of cumulative schema into a single init SQL scriptRemoval of legacy data-migration logic from startup task
This commit is a large database cleanup: BTCPay Server removed all old EF Core migration files before version 1.12.0 and replaced them with a single consolidated SQL script that creates the current schema from scratch. It also trims the st…
Large schema consolidation could silently drop or alter constraints/indexes compared to the incremental migration historyRemoval of legacy migration executors means installations upgrading from very old versions must rely on the consolidated init script and any remaining IMigrationExecutor implementationsNo explicit security claim or CVE reference in commit message or diff
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
credential or privilege state
AI analysis · High 81/100
This commit fixes a privilege escalation bug in BTCPay Server's Greenfield API. Two authorization checks were passing 'null' instead of the actual store ID when verifying whether a user could auto-approve pull payments or payouts. In BTCPay Server's authorization system, a null resource likely causes the check to fall back to a global permission evaluation, meaning a user who only had permission on one store could potentially approve or auto-approve pull payments/payouts for other stores where they should have been denied. The patch simply passes the correct storeId so the permission is scoped properly.
AI review queuedUpdate Changelogby Nicolas Dorier · 0bb223b0 · Mar 14, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update Changelog
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
This commit only updates the project's changelog file, adding one line describing a previously completed feature (wallet label filtering). It makes no code changes and has no security relevance.
AI review queuedFeat: Improved Label System - Add search filtering to label dropdown menu (#7210)by rollforsats · c5f48e7b · Mar 14, 2026 · 6 filesMessage 100 · StrongInformational 15Details
Commit message · rollforsats
Feat: Improved Label System - Add search filtering to label dropdown menu (#7210)
* improved label system - add filtering using search bar on the filter dropdown when labels exceed more than 20
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds a search box to the wallet transaction label filter dropdown. When a wallet has more than 20 labels, users can now type to search instead of scrolling through a long list. It also shows how often each label is used and lists the 20 most popular labels first. There is no security-relevant change here.
Security candidatefix: Broken Access Control: Private form access and invoice creation on other stores via unscoped authorization check (#7236)by Cerberus · e7cd630b · Mar 13, 2026 · 1 fileMessage 90 · StrongHigh 74Details
Commit message · Cerberus
fix: Broken Access Control: Private form access and invoice creation on other stores via unscoped authorization check (#7236)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access control
AI analysis · High 74/100
This commit fixes a broken access control bug in BTCPay Server's form feature. Previously, when checking whether a user could view a private form, the system asked 'Is this user allowed to view store settings anywhere?' without specifying which store. That meant any user with store-settings permission for any store could see private forms belonging to other stores, and could potentially create invoices against those stores. The patch changes the authorization check to include the specific store ID of the form, so users must have permission for that exact store.
AI review queuedRe-introduce GetAppDataby Nicolas Dorier · 62f33da3 · Mar 12, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Re-introduce GetAppData
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit simply re-adds a helper method called GetAppData that retrieves application data from a web request. It throws an error if the data is missing. There is no indication of a security fix or vulnerability in this change.
AI review queuedFix possible crash when installing pluginby Nicolas Dorier · d027a6d6 · Mar 11, 2026 · 1 fileMessage 45 · ThinInformational 16Details
Commit message · Nicolas Dorier
Fix possible crash when installing plugin
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 16/100
This is a one-line bug fix that prevents a file-move operation from failing when a destination file already exists during plugin installation. The change makes the system overwrite the existing manifest file instead of throwing an error. It appears to be a stability fix for a rare edge case rather than a security vulnerability.
AI review queuedImprove plugin crash detectionby Nicolas Dorier · e88b9ee4 · Mar 11, 2026 · 1 fileMessage 35 · OpaqueInformational 21Details
Commit message · Nicolas Dorier
Improve plugin crash detection
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
This commit improves how BTCPay Server figures out whether a crash was caused by a third-party plugin. It adds a new check that inspects the crash's stack trace to see if any loaded plugin's code appears in it. This is a defensive reliability improvement, not a fix for an active security vulnerability. It helps the server better identify misbehaving plugins so they can be disabled or reported, reducing the chance that a bad plugin causes repeated outages or unexpected behavior.
AI review queuedBump libs (#7229)by Nicolas Dorier · 35dea6af · Mar 11, 2026 · 8 filesMessage 36 · OpaqueLow 34Details
Commit message · Nicolas Dorier
Bump libs (#7229)
36/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 34/100
This commit updates several third-party software libraries and the underlying .NET runtime image used by BTCPay Server. Library and runtime updates often include routine bug fixes and security patches, but the commit message does not say any specific vulnerability was being fixed. Without a vendor security advisory or changelog reference, we cannot confirm this is a security patch, though it is a common way projects keep dependencies secure.
AI review queuedUpdate default translationsby Nicolas Dorier · 4b24455d · Mar 10, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update default translations
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
This commit only updates the default translation file for the BTCPay Server application. It adds, removes, and modifies user-facing text strings (for example, labels like 'API Key Analysis', 'Never Used', and 'Used Permissions'). There are no code logic changes, no security fixes, and no changes to how the application behaves or protects data.
AI review queuedRefactor: Cleanup useless code (#7224)by Nicolas Dorier · bab9a8a2 · Mar 10, 2026 · 25 filesMessage 65 · AdequateLow 29Details
Commit message · Nicolas Dorier
Refactor: Cleanup useless code (#7224)
65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Low 29/100
This commit is a large cleanup/refactoring change that removes unused code, simplifies controllers, and updates tests. It also removes the temporary file URL feature entirely. There are a few small security-relevant changes, such as switching pull-payment lookups to use context data set by an authorization filter and removing explicit store-id checks in some actions, but these appear to be moving checks into a shared filter rather than removing them. The commit title and message do not describe this as a security fix.
AI review queuedFix: Dashboard UI issue on mobile (#7223)by Nicolas Dorier · 134417a7 · Mar 10, 2026 · 3 filesMessage 65 · AdequateInformational 15Details
Commit message · Nicolas Dorier
Fix: Dashboard UI issue on mobile (#7223)
65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a user-interface fix for the BTCPay Server dashboard on mobile devices. It simplifies how the wallet balance widget is rendered, removes a multi-column dashboard layout, and makes the default cryptocurrency optional. There is no security-relevant change.
Security candidateInclude API key - permission analysis for improved security (#6771)by Chukwuleta Tobechi · b253df29 · Mar 10, 2026 · 11 filesMessage 96 · StrongInformational 21Details
Commit message · Chukwuleta Tobechi
Include API key - permission analysis for improved security (#6771)
* Include API key - permission analysis for improved security
resolve codderbyte
Remove designer class
fix review feedback
include text translate
avoid string parsion and use Permission directly
use permission against string
include translation and update selecte stores
Include tests for api key permission edit and usage
.Update api key analysis page
include test
delete key usage when deleting api key
* update layout and delete query
96/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
credential or privilege state
AI analysis · Informational 21/100
This commit adds a new feature that tracks which permissions each API key actually uses and shows the owner a dashboard of used, unused, and stale permissions. It is a security-hardening and visibility improvement, not a fix for an active vulnerability. The change also deletes usage records when an API key is removed.
AI review queuedUnify GetStoreDataOrNull/GetInvoiceDataOrNullby Nicolas Dorier · 08b3055e · Mar 8, 2026 · 53 filesMessage 35 · OpaqueModerate 64Details
Commit message · Nicolas Dorier
Unify GetStoreDataOrNull/GetInvoiceDataOrNull
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
This commit is a large internal cleanup that renames and unifies how BTCPay Server looks up store, invoice, app, and payment-request data from the HTTP request context. The main visible change is that many controllers stop manually checking the database for a store/invoice and instead rely on data that an authorization filter already placed in the request context. The commit also adds route-to-store mappings for paymentRequestId and pullPaymentId, and adds a new test that verifies a user with view-only invoice permission cannot read an invoice belonging to a different store. While the change is mostly defensive, it is also risky: if the authorization filter ever misses a route or a controller action is reachable without the filter, the controller may assume it has a valid store/invoice when it does not, which could lead to null-reference crashes or, in the worst case, cross-store data access.
Security candidateCleanup unused namespacesby Nicolas Dorier · 1633275d · Mar 8, 2026 · 372 filesMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Cleanup unused namespaces
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet pathboot or update pathauthentication pathparser or protocol path
AI analysis · Informational 15/100
This commit removes unused C# 'using' statements (imported namespaces) and one unused Razor view import across 372 files. It is a code-cleanup change with no functional modifications. The only non-cleanup hunk is a tiny refactor in GreenfieldInvoiceController.UpdateInvoice that reorders an existing null check and variable assignment without changing behavior.
AI review queuedHttpContext.GetStoreData method should be nullableby Nicolas Dorier · b7e69f53 · Mar 8, 2026 · 21 filesMessage 50 · ThinModerate 50Details
Commit message · Nicolas Dorier
HttpContext.GetStoreData method should be nullable
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Moderate 50/100
This commit is a code-quality and null-safety refactor. It makes the helper that retrieves the current store from an HTTP request return null when no store is set, adds a separate throw-on-null variant, and updates many controllers to use the appropriate variant. It also switches invoice lookups to use a context item set by an authorization filter. The changes reduce the chance of accidental null-reference crashes and make authorization checks more centralized, but the commit itself does not describe a specific security bug being fixed.
Security candidateRefactor: User User.GetId instead of using the UserManagerby Nicolas Dorier · be7f3f04 · Mar 8, 2026 · 44 filesMessage 62 · AdequateLow 34Details
Commit message · Nicolas Dorier
Refactor: User User.GetId instead of using the UserManager
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 34/100
This is a large internal code cleanup that replaces calls to ASP.NET Core's UserManager for getting the current user's ID with a new direct helper that reads the value from the user's identity claims. Most changes are mechanical refactors across many controllers and views. There are a few small behavior changes worth watching: the new helper returns an empty string instead of "???" for missing users, some places now treat a missing user ID as a validation failure rather than passing it through, and a couple of user-not-found cases now return NotFound instead of throwing an exception. The commit does not describe itself as a security fix and no external advisory is provided.
Security candidateFix PermissionTagHelper to behave in the right scope when in nav barby Nicolas Dorier · d6bec86c · Mar 7, 2026 · 14 filesMessage 50 · ThinLow 49Details
Commit message · Nicolas Dorier
Fix PermissionTagHelper to behave in the right scope when in nav bar
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
credential or privilege stateauthentication path
AI analysis · Low 49/100
This commit fixes how BTCPay Server's navigation bar decides which store's permissions to use when showing or hiding menu items. Previously, the permission checks inside the navigation bar could accidentally use the store from the main page (for example, the server settings page) instead of the store selected in the navigation bar. This could cause menu items to be shown or hidden incorrectly. The change makes the navigation bar temporarily switch to the correct store context while it renders, and removes a caching shortcut that could reuse the wrong permission result. There is no direct evidence in the commit message or diff that this was exploited or reported as a security vulnerability.
Security candidateDo not add claims twice for cookie authby Nicolas Dorier · e34d8d7d · Mar 6, 2026 · 1 fileMessage 50 · ThinLow 26Details
Commit message · Nicolas Dorier
Do not add claims twice for cookie auth
50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 26/100
This commit fixes a small bug where a special permission claim was being added to a user's identity every time it was transformed, instead of only once. Repeated claims are harmless in most cases, but could in theory cause the identity to grow unexpectedly or lead to subtle authorization behavior. The fix checks whether the permission claim already exists before adding it again.
Security candidatePluginize permissionsby Nicolas Dorier · 14837e6c · Mar 6, 2026 · 70 filesMessage 18 · OpaqueModerate 51Details
Commit message · Nicolas Dorier
Pluginize permissions
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
credential or privilege stateauthentication path
AI analysis · Moderate 51/100
This is a large refactoring commit that reworks how permissions are defined and enforced in BTCPay Server so that plugins can register their own permissions. It moves the permission hierarchy out of a hard-coded static class into a runtime service, changes how store context is tracked during requests, and updates authorization handlers. The change is architectural rather than a targeted security fix, but any mistake in the new permission logic could allow users to access stores or functions they should not.
AI review queuedRun CanUsePairing in CIby Nicolas Dorier · 0783c20f · Mar 2, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Run CanUsePairing in CI
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only changes test code. It fixes a minor indentation issue and adds a test category label so that an existing test called CanUsePairing is run as part of automated browser-based (Playwright) testing. There is no change to production code, no bug fix, and no security relevance.
Security candidateDecrease logs about challenged authentication schemesby Nicolas Dorier · 54056a40 · Mar 2, 2026 · 2 filesMessage 55 · ThinInformational 15Details
Commit message · Nicolas Dorier
Decrease logs about challenged authentication schemes
55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 15/100
This commit simply turns down the volume on log messages coming from BTCPayServer's security components. It changes the logging level from the default (likely Information/Debug) to Warning, so routine 'authentication scheme challenged' messages no longer fill the logs. There is no code behavior change, no bug fix, and no security vulnerability being patched.
AI review queuedFix flaky testby Nicolas Dorier · d9d50a70 · Mar 2, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix flaky test
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only changes a test file to make an automated test less flaky. It adds checks so the test waits for the correct payout event and allows empty hooks in one specific scenario. There is no change to production code and no security issue.
AI review queuedApply csrf protection on all UI**Controller globally (#7199)by Nicolas Dorier · 9bf54970 · Mar 1, 2026 · 37 filesMessage 58 · ThinHigh 83Details
Commit message · Nicolas Dorier
Apply csrf protection on all UI**Controller globally (#7199)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · High 83/100
This commit strengthens BTCPay Server's defenses against cross-site request forgery (CSRF) attacks. Instead of manually adding CSRF protection to each web UI controller, the team added a single global filter that automatically checks CSRF tokens for all UI controllers. They also converted several API (Greenfield) controllers from the web-style Controller base class to the API-style ControllerBase so the global filter does not accidentally apply CSRF checks to API endpoints. A few endpoints that legitimately need to skip CSRF (such as the error page and invoice state changes) are explicitly marked to ignore it. The change is a security hardening patch, but the commit message and diff alone do not prove a specific exploitable vulnerability existed before.
AI review queuedMigrate Bitcoin Core 30.2 (#7213)by Nicolas Dorier · e2788bd1 · Mar 1, 2026 · 5 filesMessage 53 · ThinInformational 18Details
Commit message · Nicolas Dorier
Migrate Bitcoin Core 30.2 (#7213)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100
This commit updates BTCPay Server's automated test environment to use Bitcoin Core version 30.2 instead of 29.1. It also adjusts a few test helper calls and one test assertion to match changed behavior in the newer Bitcoin Core version. There is no direct evidence in the commit of a security vulnerability being fixed or introduced.
Security candidateRefactor: Move Bitpay stuff in its own pluginby Nicolas Dorier · 39d99f0b · Feb 27, 2026 · 55 filesMessage 57 · ThinLow 35Details
Commit message · Nicolas Dorier
Refactor: Move Bitpay stuff in its own plugin
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 35/100
This commit is a large code refactor that moves BTCPay Server's Bitpay-compatible API from the core application into a separate plugin. It relocates controllers, authentication, models, views, and middleware into a new Plugins/Bitpay folder, updates tests and dependency injection, and replaces the old middleware-based Bitpay API detection with a new endpoint selector policy. The change itself is structural rather than a targeted security fix, but any large refactor of authentication and routing code carries a risk of accidentally changing access-control behavior.