LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16016: Sanitize-html is a library for scrubbing html input of malicious values.

Sanitize-html is a library for scrubbing html input of malicious values. Versions 1.11.1 and below are vulnerable to cross site scripting (XSS) in certain scenarios: If allowed at least one nonTextTags, the result is a potential XSS vulnerability.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-16016 affects the sanitize-html Node module, a library often trusted to remove unsafe HTML. Versions 1.11.1 and earlier could fail in certain configurations, allowing cross-site scripting when at least one nonTextTags value is allowed. Business risk depends on whether applications sanitize untrusted HTML with this library and configuration.

Executive priority

Treat as a targeted dependency review, not an emergency based on the supplied evidence. Prioritize internet-facing or multi-user systems that render user-submitted HTML, because successful XSS can affect users, sessions, and trust in affected workflows.

Technical view

The issue is CWE-79 cross-site scripting in sanitize-html <=1.11.1. The source description says XSS is possible when the sanitizer is configured to allow at least one nonTextTags entry. The bundle provides a GitHub issue and commit reference, but no CVSS score or fixed release number.

Likely exposure

Exposure is likely in Node.js applications using sanitize-html 1.11.1 or earlier to process user-controlled HTML, especially where nonTextTags are allowed. Applications that do not use this package, use later fixed versions, or do not sanitize untrusted HTML through this configuration are less likely exposed.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not listed as KEV in the bundle. Practical impact would usually require an application path where attacker-controlled HTML is sanitized with the vulnerable configuration and then rendered to users.

Researcher notes

Evidence is limited to the CVE description, advisory link, GitHub issue, and commit reference. Severity scoring, exploit availability, and fixed version details are not included in the supplied bundle. Validate exposure by dependency version, configuration, and reachable rendering paths.

Mitigation direction

  • Inventory applications and dependencies for sanitize-html versions 1.11.1 or earlier.
  • Review sanitizer configuration for allowed nonTextTags handling.
  • Upgrade away from affected versions after confirming vendor guidance or fixed release notes.
  • Review the referenced upstream commit and issue for remediation context.
  • Prioritize user-facing applications that render sanitized user HTML.

Validation and detection

  • Check package manifests and lockfiles for sanitize-html dependency versions.
  • Confirm whether untrusted HTML reaches sanitize-html before rendering.
  • Inspect application configuration for allowed nonTextTags entries.
  • Review rendered output paths for stored or reflected user HTML.
  • Record evidence when affected code paths are absent or unreachable.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-16016 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HackerOnesanitize-html node module<=1.11.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.