LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11022: jQuery has a potential XSS vulnerability

In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Older jQuery versions can turn attacker-influenced HTML into script execution when an application inserts that HTML into the page. The risk is not every jQuery use; it matters when untrusted HTML reaches DOM manipulation methods. Successful exploitation could expose user data or perform actions in a victim's browser session.

Executive priority

Treat as a moderate web security remediation item. Prioritize internet-facing and authenticated business portals first, especially where users can submit rich text, HTML-like content, comments, templates, or imported third-party content.

Technical view

CVE-2020-11022 is a CWE-79 XSS issue in jQuery versions 1.12.0 through before 3.5.0. Passing untrusted HTML, even after sanitization, into methods such as .html() or .append() may execute code. The supplied CVSS is 6.9 with network attack vector, high complexity, no privileges, and required user interaction.

Likely exposure

Exposure is most likely in public web applications, admin consoles, embedded widgets, or packaged products bundling affected jQuery and inserting user-controlled HTML. Sites only using jQuery for static selectors or events may not be practically exposed, but version inventory alone is not enough.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation. It does include public security advisories and exploit-reference material, so defenders should assume the behavior is known and testable while avoiding claims of confirmed exploitation.

Researcher notes

Key validation is data-flow based: identify affected jQuery versions, then prove whether attacker-controlled HTML can reach jQuery DOM insertion APIs. The advisory names the vulnerable pattern and fixed version, but the bundle does not provide environment-specific exploitability or product-by-product remediation details.

Mitigation direction

  • Upgrade jQuery to 3.5.0 or later where application compatibility allows.
  • Apply vendor or distribution updates for software that bundles jQuery.
  • Audit uses of .html(), .append(), and related DOM insertion methods.
  • Avoid sending untrusted HTML into jQuery DOM manipulation paths.
  • Review sanitizer assumptions because the advisory says sanitized HTML may still be unsafe.

Validation and detection

  • Inventory production bundles for jQuery versions from 1.12.0 to before 3.5.0.
  • Map affected jQuery use to routes accepting user-controlled or third-party HTML.
  • Confirm built assets load jQuery 3.5.0 or later after remediation.
  • Review downstream vendor advisories for packaged applications using bundled jQuery.
  • Run regression tests around pages changed by the jQuery upgrade.
Prepared
Confidence
high
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-11022 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
41Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N1.64.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.9Medium
CVSS 3.1 vector shape for CVE-2020-11022Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
jqueryjQuery>= 1.12.0, < 3.5.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

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

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.