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

Apply store’s language on customer-facing pages (#7656)

Public commit record

What the developer wrote

Authored by Chukwuleta Tobechi

58/100 · Thin
Apply store’s language on customer-facing pages (#7656)
✓ 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 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 direct evidence in the commit that this fixes an active security vulnerability; it reads as a feature or hardening change to make customer-facing language selection consistent and to prevent a SignalR hub from bypassing the store-language logic.

Recommended action

Treat as a regular feature/hardening patch. Review that RouteStoreResolver cache invalidation is acceptable (10-minute sliding cache on store-id lookups) and that the new UseStoreLanguage filter does not interfere with admin UI language selection. No urgent security deployment is indicated by the diff alone.

Security signals we found

01

New per-request language scoping via AsyncLocal with explicit BeginRequest/Restore disposal

02

SignalR hub now applies store language to controller calls that bypass MVC filters

03

RouteStoreResolver centralizes route-value-to-store-id lookup with 10-minute sliding memory-cache

04

StorefrontLanguage input is validated against installed translations in GeneralSettings POST

05

Refactored permission scope provider now reuses the same resolver, reducing duplicated SQL lookup logic

Risk score

Why this scored 24/100

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