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

Preserve unresolved template expressions

Public commit record

What the developer wrote

Authored by Nicolas Dorier

35/100 · Opaque
Preserve unresolved template expressions
✓ Descriptive subject! No meaningful explanatory body
The short version

What changed, and why it matters

This commit changes how BTCPay Server fills in template placeholders (like {OrderId} or {InvoiceId}) in URLs, payment descriptions, and point-of-sale button text. Previously, if a placeholder could not be resolved or had a syntax error, it was replaced with a visible error string such as [NotFound(...)] and could also be URL-encoded, making it unreadable. The new behavior preserves the original placeholder expression unchanged when it cannot be resolved, and adds a dedicated URL template helper that properly encodes resolved values while leaving unresolved placeholders intact. The change is described as a fix/polish rather than a security patch, but it reduces the risk of broken or misleading URLs and user-facing strings.

Recommended action

Treat as a hardening/usability fix rather than an urgent security patch. Review whether user-supplied template strings are validated or escaped to prevent injection of unexpected placeholders or malformed expressions. Continue monitoring for related security advisories from the BTCPay Server project.

Security signals we found

01

Template engine fallback behavior changed from error-string substitution to literal placeholder preservation

02

URL template helper introduced to encode resolved values while not encoding unresolved placeholders

03

Multiple user-controlled template inputs rendered into URLs and payment metadata

04

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

05

No input sanitization or allowlist added for template expressions

Risk score

Why this scored 35/100

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