Threats / JQuery / CVE-2020-11023
CVE-2020-11023
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
JQuery vulnerability
jQuery contains a persistent cross-site scripting vulnerability in DOM manipulators that can execute untrusted code when processing maliciously formed HTML input.
Verdict
Today item — known-exploited.
Attackers can inject persistent XSS payloads through DOM manipulation functions in jQuery, allowing arbitrary script execution in users' browsers and potential session hijacking, credential theft, or malware distribution.
CISA KEV Yes · 2025-01-235EPSS 0.84887 (verify live)6CVSS 6.93CISA SSVC Exploitation: active · Automatable: no · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-01-23).
Probability (EPSS)
EPSS 0.84887 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 6.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N) · Affected: JQuery, JQuery. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-79 Cross-site Scripting (XSS) — weakness family: Web / client.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1730 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft malicious HTML containing script payloads and submit it through application input fields that use jQuery DOM manipulators.
Business
Attackers gain ability to execute arbitrary JavaScript in user browsers, compromising session security and user data.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I ensure the payload persists in the application's data store so it executes for all subsequent users viewing the affected content.
Business
The vulnerability scales to affect multiple users, increasing exposure and potential for widespread credential compromise or malware infection.
3
Lateral reach — past segmentation narrative 3
Attacker
I use the injected script to steal session tokens, redirect users to phishing sites, or install keyloggers.
Business
User accounts are compromised, sensitive data is exfiltrated, and customer trust in the application is severely damaged.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by GitHub_MCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.