Advisory

GHSA-3753-m2x2-q623

Also known as: CVE-2026-91127

Summary

File Viewer: DOM XSS via unsafe hyperlink schemes in the legacy DOC renderer

Details

Summary

Before 2.3.1, the legacy .doc renderer emitted document hyperlink targets after HTML escaping but without a URL-scheme allowlist. A crafted .doc could therefore render a live javascript:, vbscript:, data:, or similarly unsafe link. Script could execute in the embedding origin if a viewer clicked it.

Impact

Applications rendering untrusted legacy .doc files with @file-viewer/doc or the msdoc-viewer compatibility package could expose their origin to attacker-controlled script after link interaction.

Fix

Version 2.3.1 centralizes link handling, removes control-character and scheme confusion, blocks external document links by default, and in explicit allow mode accepts only HTTP(S), mail, telephone, safe relative URLs, and internal bookmarks. The renderer output is safe before mounting, with mount-boundary sanitization as defense in depth. The msdoc-viewer compatibility release containing the fix is 0.2.2.

Thanks to @shashank420 for responsibly reporting this issue.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-09-18 17:19 UTC
Modified
2026-09-18 17:30 UTC

Affected packages and fixes

@file-viewer/doc

npm · All systems

Affected

  • introduced 0, fixed 2.3.1 (semver)

Fixed versions

2.3.1

Fix

msdoc-viewer

npm · All systems

Affected

  • introduced 0, fixed 0.2.2 (semver)

Fixed versions

0.2.2

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences