fix(security): escape untrusted scan fields in dashboard history - #1117

Draft

seonghobae wants to merge 14 commits into

sentinel-fix-xss-scan-id-3067697822450697100

Commits on Sep 5, 2026

🛡️ Sentinel: [CRITICAL] Fix DOM XSS in Scan History Table
seonghobae
committed
0c4d9f5

Commits on Sep 6, 2026

🛡️ Sentinel: [CRITICAL] Fix DOM XSS via Unescaped Scan ID in History Table
seonghobae
committed
652f8ea
🛡️ Sentinel: [CRITICAL] Fix DOM XSS via Unescaped Scan ID in History Table
seonghobae
committed
5f9ba02
🛡️ Sentinel: [CRITICAL] Fix DOM XSS via Unescaped Scan ID in History Table
seonghobae
committed
b7b0dde
test: remove unused dashboard fixture read
seonghobae
committed
3c43029
test: assert scan id cannot inject an element
seonghobae
committed
b382f52
🛡️ Sentinel: [CRITICAL] Fix DOM XSS via Unescaped Scan ID in History Table
seonghobae
committed
7638d95
🛡️ Sentinel: [CRITICAL] Fix DOM XSS via Unescaped Scan ID in History Table
seonghobae
committed
ff519df
🛡️ Sentinel: [CRITICAL] Fix DOM XSS via Unescaped Scan ID in History Table
seonghobae
committed
b018581
test: restore DOM injection oracle after concurrent update
seonghobae
committed
6930c8d
fix(test): preserve dashboard selector assertions
seonghobae
committed
be303c2
test: expose hostile dashboard summary counts
seonghobae
committed
b29c0ab
fix(console): coerce summary counts before HTML rendering
seonghobae
committed
0679fcb
test: carry hostile dashboard text-field coverage
seonghobae
committed
d3283a1