Skip to content

fix(formatter): prevent stored XSS by disabling default HTML safety#29

Merged
Ruesa18 merged 1 commit into
1.0-devfrom
fix/vuln-stored-xss
Jun 18, 2026
Merged

fix(formatter): prevent stored XSS by disabling default HTML safety#29
Ruesa18 merged 1 commit into
1.0-devfrom
fix/vuln-stored-xss

Conversation

@Ruesa18

@Ruesa18 Ruesa18 commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

@Ruesa18
Ruesa18 force-pushed the fix/vuln-stored-xss branch from daf6090 to b7f00fa Compare June 18, 2026 11:50
Formatters no longer treat their output as HTML safe by default. This closes a stored XSS vector where unsanitized user input could inject script content.

Existing formatters must now explicitly implement isHtmlSafe() to return true *and* ensure proper escaping/sanitization before claiming safety.

BREAKING CHANGE: Default formatter behavior changed; outputs are now considered unsafe HTML unless explicitly marked safe. Audit custom formatter implementations.
@Ruesa18
Ruesa18 force-pushed the fix/vuln-stored-xss branch from b7f00fa to 11e9708 Compare June 18, 2026 12:45
@Ruesa18
Ruesa18 merged commit f469cba into 1.0-dev Jun 18, 2026
2 checks passed
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.

2 participants