LiveActive security incident?Get immediate response
CVE Record

CVE-2018-6341: React applications which rendered to HTML using the ReactDOMServer API were not escaping user-supplied attr...

React applications which rendered to HTML using the ReactDOMServer API were not escaping user-supplied attribute names at render-time. That lack of escaping could lead to a cross-site scripting vulnerability. This issue affected minor releases 16.0.x, 16.1.x, 16.2.x, 16.3.x, and 16.4.x. It was fixed in 16.0.1, 16.1.2, 16.2.1, 16.3.3, and 16.4.2.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-6341 is an XSS issue in React server-side rendering. Some React applications using ReactDOMServer did not escape user-supplied attribute names when generating HTML. If an attacker could influence those attribute names and a user viewed the resulting page, script execution could occur.

Executive priority

Treat this as a targeted moderate-risk dependency issue. It warrants remediation where older server-rendered React is exposed to users, but the provided evidence does not support emergency handling for active exploitation.

Technical view

The flaw affects react-dom minor lines 16.0.x through 16.4.x before the listed fixed patch releases. It is CWE-79 with CVSS 3.1 score 6.1. The vulnerable path is ReactDOMServer render-time HTML generation when user-supplied attribute names are emitted without escaping.

Likely exposure

Exposure is most likely in older server-rendered React applications pinned to affected react-dom 16.0.x through 16.4.x versions and accepting dynamic attribute names from untrusted input. Client-only React applications are less directly indicated by the source description.

Exploitation context

The provided sources do not state known active exploitation, and the CVE is not marked KEV. The CVSS vector indicates network reachability, low attack complexity, no privileges, and user interaction required, consistent with reflected or stored XSS impact when vulnerable rendering is reachable.

Researcher notes

Key evidence is narrow: ReactDOMServer, user-supplied attribute names, and affected 16.0.x through 16.4.x minor lines with specific fixed patch releases. Do not broaden this to all React usage without confirming server-side rendering and vulnerable dependency versions.

Mitigation direction

  • Upgrade react-dom to 16.0.1, 16.1.2, 16.2.1, 16.3.3, 16.4.2, or later as applicable.
  • Check React vendor release guidance before choosing a target version.
  • Avoid rendering untrusted input as attribute names through ReactDOMServer.
  • Prioritize internet-facing SSR applications and user-generated content paths.

Validation and detection

  • Inspect package manifests and lockfiles for react-dom 16.0.x through 16.4.x versions.
  • Confirm whether the application uses ReactDOMServer for server-side HTML rendering.
  • Review SSR code paths for dynamic attribute names influenced by users.
  • Verify upgraded builds resolve to a fixed react-dom patch level.
Prepared
Confidence
high
Sources
4

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-2018-6341 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
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2018-6341Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Facebookreact-dom16.4.2, 16.4.0, 16.3.3, 16.3.0, 16.2.1, 16.2.0, 16.1.2, 16.1.0, 16.0.1, 16.0.0, unspecifiedListed
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.