Skip to content
Noroxi
NVD / CVE Program· CNA facebook

CVE-2018-6341: React applications which rendered to HTML using the ReactDOMServer API were not escaping user-supplied attribute names at render-time.

MediumCVSS 6.1 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Monitor (action score 25/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 3.4% (FIRST EPSS); higher than 89% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: Facebook react-dom 16.0.1.

Low priority for now. Upgrade to Facebook react-dom 16.0.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Dec 31, 2018
Updated
Jun 16, 2026
EPSS
3.4% · 89th percentile

Report tools

JSON

Action score

25

Monitor

Low priority for now.

CVSS
24 / 40 · 6.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2018-6341

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Is the React DOM on your site affected?Scan JavaScript libraries

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is the React DOM on your site affected?Scan JavaScript libraries

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
facebookreact

Is the React DOM on your site affected?

The free JavaScript library scanner reads the React DOM version from the files your site loads, matches this record and other known vulnerabilities, and gives the safe version on the same branch. If the version can't be read, it says so. No account needed.

Scan JavaScript libraries

Versions reported by the vendor

Affected version ranges reported by the assigning authority (facebook). Independent of NVD's CPE analysis and usually ahead of it.

  • Facebook react-dom

    • 16.4.2, 16.3.3, 16.2.1, 16.1.2, 16.0.1affected
    • 16.4.0 and later · before unspecifiedaffected
    • 16.3.0 and later · before unspecifiedaffected
    • 16.2.0 and later · before unspecifiedaffected
    • 16.1.0 and later · before unspecifiedaffected
    • 16.0.0 and later · before unspecifiedaffected
    • unspecified and later · before 16.0.0not affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmreact-domfrom 16.0.0 · before 16.0.116.0.1
npmreact-domfrom 16.1.0 · before 16.1.216.1.2
npmreact-domfrom 16.2.0 · before 16.2.116.2.1
npmreact-domfrom 16.3.0 · before 16.3.316.3.3
npmreact-domfrom 16.4.0 · before 16.4.216.4.2

Other highest-scoring records for the same primary product.

  • CVE-2025-55182A pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0…KEV
    100Now
  • CVE-2025-55184A pre-authentication denial of service vulnerability exists in React Server Components versions 19.0.0, 19.0.1 19.1.0, 19.1.1, 19.1.2, 19.2.
    49Plan
  • CVE-2025-67779It was found that the fix addressing CVE-2025-55184 in React Server Components was incomplete and does not prevent a denial of service…
    35Monitor

Published before and after this one in the same product

  • Later →CVE-2026-23864Jan 26, 2026 · Multiple denial of service vulnerabilities exist in React Server Components, affecting the following packages: react-server-dom-parcel…
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Facebook react-dom16.0.1 · descriptionVendor (CNA)
npm:react-dom16.0.1Package registry (OSV)
npm:react-dom16.1.2Package registry (OSV)
npm:react-dom16.2.1Package registry (OSV)
npm:react-dom16.3.3Package registry (OSV)
npm:react-dom16.4.2Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02023-03-20

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+1539 d
  3. TodayNov 13, 2026+2874 d

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

CVSS vector

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

nvd-secondary

Root cause

User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
commentEl.innerHTML = comment.body;

Fixed

ts
commentEl.textContent = comment.body;

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records