Skip to content
Noroxi
CVE-2018-6341· NVD / CVE Program· CNA facebook

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

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.1 · v3.1—Proof of concept Fix available
Published
Dec 31, 2018
Updated
Jun 16, 2026
EPSS
3.4% · 88th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

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.

Affected systems

VendorProduct
facebookreact

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • facebook react16.0.0 and later · before 16.0.1
  • facebook react16.1.0 and later · before 16.1.2
  • facebook react16.2.0 and later · before 16.2.1
  • facebook react16.3.0 and later · before 16.3.3
  • facebook react16.4.0 and later · before 16.4.2

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

Same product

facebook: all records

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 incluKEV
    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.
    50Plan
  • 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 attac
    36Monitor
  • CVE-2026-23864Multiple denial of service vulnerabilities exist in React Server Components, affecting the following packages: react-server-dom-parcel, reac
    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. TodaySep 29, 2026+2829 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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

Weakness class (CWE)

CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

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.

The bug in code

The whole CWE-79 class

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;

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

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

All records