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

Fix PermissionTagHelper to behave in the right scope when in nav bar

Public commit record

What the developer wrote

Authored by Nicolas Dorier

50/100 · Thin
Fix PermissionTagHelper to behave in the right scope when in nav bar
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

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.

Recommended action

Treat this as a defense-in-depth UI authorization fix. Review whether any nav-bar links were previously visible to users who lacked the corresponding store permission under the old logic, and consider whether a security advisory is warranted if any sensitive action could be reached through those links. No immediate emergency patching is indicated by the supplied materials alone.

Security signals we found

01

Authorization scope confusion between page context and navigation component context

02

Removal of cached authorization results in PermissionTagHelper, which could have returned stale/wrong decisions

03

Addition of explicit store context switching (SwitchStoreData) for nav bar rendering

04

Refactoring of implicit store ID resolution into a single scope provider

05

No explicit security advisory, CVE, or exploit description in commit or supplied references

Risk score

Why this scored 49/100

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