Research / Finding
enhancement: avoid template.JSStr
F-TREZOR-BLOCKBOOK-NFT-URI-XSS-001
Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.
Read the evidence · View in research browse
Recorded evidence
—score not recorded
enhancement: avoid template.JSStr
merged
details
- Finding IDs
- F-TREZOR-BLOCKBOOK-NFT-URI-XSS-001
- Status
- merged
- Reported via
- security contact
- Note
- public fix commit e4fdb5ee25a5 on 2026-03-16. removes the template.JSStr path in token detail rendering and adds regression coverage for XSS-safe escaping.
F-TREZOR-BLOCKBOOK-NFT-URI-XSS-001: Code / markup injection. An NFT URI reaches executable markup without the required escaping. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.
Mechanism source for F-TREZOR-BLOCKBOOK-NFT-URI-XSS-001
Security area (1seal assessment): Semantics. An NFT URI reaches executable markup without the required escaping. Reviewed 24 Sep 2026.
Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.
How this page groups evidence
This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.