Security readout for executives and security teams
Plain-English summary
striptags versions before 3.2.0 can mishandle non-string input. If an application sends attacker-controlled array-like data into the library, unsanitized text may reach a webpage and create XSS risk. The public sources rate this as low severity with high attack complexity, but exposed web inputs still warrant dependency cleanup.
Executive priority
Treat this as a low-severity dependency hygiene issue unless the library processes public web input. Prioritize remediation in internet-facing applications where sanitized output is rendered into pages or templates.
Technical view
CVE-2021-32696 is a type-confusion flaw in ericnorris/striptags <3.2.0. The html parameter can receive an array-like object; internal concatenation may preserve unsanitized strings instead of stripping tags. The advisory maps this to CWE-241 and CWE-79, with CVSS 3.1 score 3.7.
Likely exposure
Most likely in Node.js or TypeScript applications using striptags before 3.2.0 and passing request data, especially query parameters, directly to the html argument. Applications only passing trusted strings are less exposed, based on the advisory's described precondition.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. Abuse requires attacker control over the input shape reaching striptags, not merely normal string content. Impact is described as potential XSS and limited confidentiality exposure.
Researcher notes
The key condition is type confusion on the html parameter with array-like input. The public bundle identifies the fix release and commit, but does not provide evidence of exploitation in the wild. Validate exposure through call-site review, not package presence alone.
Mitigation direction
- Upgrade striptags to version 3.2.0 or later.
- Reject or normalize non-string values before calling striptags.
- Review routes that pass query parameters directly into striptags.
- Check upstream advisory and release notes for vendor guidance.
Validation and detection
- Inspect dependency manifests and lockfiles for striptags versions below 3.2.0.
- Trace user-controlled request data into striptags html arguments.
- Add regression tests covering non-string html inputs.
- Confirm deployed builds include the upgraded dependency version.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-241: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCWE-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 lookupCVE-2021-32696 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N2.21.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.7LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ericnorris/striptags/security/advisories/GHSA-qxg5-2qff-p49rCVE reference · x_refsource_CONFIRM
- https://github.com/ericnorris/striptags/commit/f252a6b0819499cd65403707ebaf5cc925f2facaCVE reference · x_refsource_MISC
- https://github.com/ericnorris/striptags/releases/tag/v3.2.0CVE reference · x_refsource_MISC
- https://www.npmjs.com/package/striptagsCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Handling of Unexpected Data Type
Improper Handling of Unexpected Data Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.