Skip to content

docs: say that the payer's message and name are untrusted, and where injection is stopped - #42

Merged
landsman merged 1 commit into
mainfrom
untrusted-text
Nov 10, 2026
Merged

landsman merged 1 commit into
mainfrom
untrusted-text

Conversation

@landsman

Copy link
Copy Markdown
Owner

A valid DKIM signature proves the bank sent the e-mail, not that the payer's message is harmless. Nothing said so. usage.md and llms.txt now do: message() and counterName() are handed out as written, plain text, unescaped, so SQL binds them as parameters and templates escape them.

The library does not sanitise them itself: it cannot know where the text goes, escaping for HTML does nothing against SQL injection, and a changed message could stop matching an invoice. jsoup's Cleaner was considered for it and left out for those reasons (and its own CVE-2022-36033 and CVE-2026-71497).

Docs only.

@landsman
landsman merged commit 5a8fc91 into main Nov 10, 2026
2 checks passed
@landsman
landsman deleted the untrusted-text branch November 10, 2026 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant