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

Merge pull request #7750 from btcpayserver/fix/vue-stored-template-xss

Public commit record

What the developer wrote

Authored by Nicolas Dorier

58/100 · Thin
Merge pull request #7750 from btcpayserver/fix/vue-stored-template-xss

Keep stored text out of Vue templates
✓ 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 merge commit appears to fix a stored cross-site scripting (XSS) issue in BTCPay Server's Vue.js templates. The changes prevent user-controlled text (wallet labels, form configuration JSON, and validation output) from being processed by Vue, which could otherwise allow an attacker to inject malicious JavaScript that runs in another user's browser. The patch uses the `v-pre` directive to tell Vue to skip certain HTML elements, and moves form configuration data out of a Vue-bound textarea into a plain JavaScript variable.

Recommended action

Review all remaining Razor/Vue views for similar patterns where user-controlled or stored text is placed inside Vue templates without `v-pre` or proper escaping. Audit the `Safe.Json` serializer to confirm it escapes forward slashes and HTML-special characters appropriately for JavaScript context. Consider adding automated tests or a lint rule that flags unescaped user content inside Vue templates.

Security signals we found

01

Branch name explicitly references 'vue-stored-template-xss'

02

Use of `v-pre` to prevent Vue compilation of user-controlled content

03

Migration of JSON config from Vue-bound textarea to a plain JS variable serialized with `Safe.Json`

04

Stored XSS context: labels and form config are persisted server-side and rendered to other users

05

Partial patch: only four files changed; other Vue templates may remain unreviewed

Risk score

Why this scored 75/100

Our methodology →
Potential impact 22/30
Exploitability 18/25
Stealth signal 12/15
Affected reach 12/15
Confidence 7/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.