Skip to main content
Mallory
UnratedVulnerability

CVE-2013-7035: Cross-site scripting in React key generation

Updated 5 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2013-7035CWE-79

CVE-2013-7035 is a cross-site scripting vulnerability in React affecting 0.5.x before 0.5.2 and 0.4.x before 0.4.2. According to the provided advisory, the issue is caused by improper sanitization of input used to create keys. If an application derives a React key from attacker-controlled input, the unsanitized value can be incorporated in a way that enables script execution in the victim's browser context.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow arbitrary JavaScript execution in the context of the affected user's browser session. This can enable session theft, DOM manipulation, data exfiltration, phishing within the trusted origin, and other client-side actions available to injected script under the application's origin.

Mitigation

If you can’t patch tonight, do this now.

Avoid generating React keys from untrusted or user-controlled input. Where such input cannot be avoided, validate and sanitize it before use, and reduce XSS impact with standard browser-side controls such as a restrictive Content Security Policy. These measures are compensating controls; upgrading to a fixed React version is the primary remediation.

Remediation

Patch, then assume compromise.

Upgrade React 0.5.x to version 0.5.2 or later, or React 0.4.x to version 0.4.2 or later, as specified in the advisory.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2013-7035 exploited in the wild?
As of Jun 12, 2026, Mallory has no reports of CVE-2013-7035 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2013-7035?
As of Jun 12, 2026, Mallory has found no public exploit for CVE-2013-7035.
Is there a patch for CVE-2013-7035?
Upgrade React 0.5.x to version 0.5.2 or later, or React 0.4.x to version 0.4.2 or later, as specified in the advisory.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.