CVE-2018-6341 — React applications which rendered to HTML using the ReactDOMServer API were not

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

01What is this vulnerability?

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.

02Affected products

Vendor	Product	Versions
Facebook	react	dom — 16.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, unspecified

03Active exploitation status

Not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. EPSS is the best forward-looking signal — see the EPSS row above.

04Recommended remediation

• Patch to a fixed version listed in the vendor advisory (see references below).
• Mitigate with WAF rules, network egress filters, or feature flags where the patch is not yet available.
• Hunt historical logs for exploitation indicators — see Detection signatures below.

05Technical details

For the full vendor write-up, exploit chains, and reference implementations, see the references list in section 09.

06Detection signatures

Ask SARA in chat to draft a starting detection for this CVE in your stack of choice.

07Related CVEs

No directly-cited follow-up CVEs in the KB record for this advisory. The references list in section 09 carries the vendor cross-references.

08Timeline

• Published: 2018-12-31T22:00:00.000Z
• Last modified: 2025-05-06T16:54:17.932Z

09References

• reactjs.org — https://reactjs.org/blog/2018/08/01/react-v-16-4-2.html
• twitter.com — https://twitter.com/reactjs/status/1024745321987887104