Vulnerability · CVE-2018-6341
React applications which rendered to HTML using the ReactDOMServer API were not escaping user-supplied attribute names at render-time.
Published Dec 31, 2018 · catalog updated Jun 17, 2026 · React applications which rendered
Last checked Nov 8, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2018-6341. EPSS is 3.43%. Act only if a listed version of React applications which rendered is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (React applications which rendered).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-23864 · High
- CVE-2025-55184 · High · known exploited
- CVE-2025-55182 · Critical · known exploited
- Severity
- Medium6.1
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 3.43%
- Remediation
- Version ranges on file
- Affected products
- cpe facebook/react
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe facebook/react< 16.0.1
- cpe facebook/react< 16.1.2
- cpe facebook/react< 16.2.1
- cpe facebook/react< 16.3.3
- cpe facebook/react< 16.4.2
How to fix CVE-2018-6341
Upgrade
CVE-2018-6341 lists a fix boundary at 16.0.1. Compare the installed build with that boundary before you change production.
Version check
Affected < 16.0.1
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2018-6341. EPSS is 3.43%. Act only if a listed version of React applications which rendered is installed.
Which versions are affected?
Compare what you have installed with < 16.0.1, < 16.1.2, < 16.2.1, < 16.3.3, < 16.4.2. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-79: Cross-site Scripting (XSS). EPSS 3.43%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Dec 31, 2018 · Monitored products — high
Detected
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.
Jun 17, 2026 · Monitored products — high
Updated
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.
Sources
- CVE.orgVulnerability recordCVE-2018-6341
Official CVE identifier
cve.org - Monitored products — highVendor advisoryCVE-2018-6341
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.
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 8, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgNov 8, 2026
- Monitored products — highNov 8, 2026