CVE-2026-30691
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Scripting (XSS) vulnerability in @cyntler/react-doc-viewer v1.17.1 allows remote attackers to execute arbitrary JavaScript via a crafted .txt file. The TXTRenderer component fails to sanitize file content and explicitly casts raw data as a ReactNode
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe TXTRenderer component in @cyntler/react-doc-viewer v1.17.1 contains a cross-site scripting vulnerability where .txt file content is rendered without sanitization. The component explicitly casts raw file data as a ReactNode, allowing attackers to embed malicious JavaScript in crafted .txt files that will execute in victims' browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of react-doc-viewerRun 'npm list @cyntler/react-doc-viewer' or check package.json dependencies to retrieve the exact installed version numberAffected if The installed version is v1.17.1 specifically (or any version prior to patched release that contains the vulnerable TXTRenderer)
-
Verify TXTRenderer is in useSearch project codebase for imports or usage of TXTRenderer component, typically found as 'import { TXTRenderer } from "@cyntler/react-doc-viewer"' or similar patterns in renderer configurationAffected if TXTRenderer component from @cyntler/react-doc-viewer is imported and used in the application
-
Confirm .txt file handling is enabledInspect the DocViewer configuration to see if .txt or text/plain is listed in the supported document formats, often in a documents array or file type mappingAffected if The application is configured to render .txt files using the react-doc-viewer library
-
Check for output rendering of raw text contentReview how TXTRenderer processes and outputs text file content in the codebase - look for direct rendering of raw data as ReactNode without sanitizationAffected if Text files are being rendered directly without sanitization (e.g., no DOMPurify, no escaping) in the viewer component
A user is affected if their application uses @cyntler/react-doc-viewer v1.17.1 (or earlier vulnerable version) with TXTRenderer enabled to display .txt files, allowing malicious JavaScript embedded in those files to execute.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement input sanitization in the TXTRenderer component to escape or strip HTML/script content before rendering file contents as React nodes. Consider using a library like DOMPurify to sanitize text content.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30691 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30691 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data