What changed, and why it matters
This is a small user-interface fix in a wallet settings dropdown. Previously, if no specific currencies were configured as allowed, the currency selector showed an empty list. Now it falls back to showing the full list of available currencies. There is no indication this is a security issue.
No security action needed. Treat as a normal UI/UX fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The Vue component lnbits-wallet-extra.vue now passes g.currencies as the q-select options when g.allowedCurrencies is empty, instead of passing an empty array. This restores expected UI behavior when allowedCurrencies is unspecified. No input validation, authorization, or backend logic is changed.
Changed components
lnbits/templates/components/lnbits-wallet-extra.vueInspect captured patch +5 / −1
diff --git a/lnbits/templates/components/lnbits-wallet-extra.vue b/lnbits/templates/components/lnbits-wallet-extra.vue
index f008b1f..7517276 100644
--- a/lnbits/templates/components/lnbits-wallet-extra.vue
+++ b/lnbits/templates/components/lnbits-wallet-extra.vue
@@ -128,7 +128,11 @@
@change="updateWallet({currency: g.wallet.currency})"
type="text"
:disable="g.fiatTracking"
- :options="g.allowedCurrencies"
+ :options="
+ g.allowedCurrencies.length > 0
+ ? g.allowedCurrencies
+ : g.currencies
+ "
:label="$t('currency_settings')"
></q-select>
</div>
Why this scored 18/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.