Subscriber Cross Site Scripting (XSS) in Awesome Support <= 6.3.9 versions.
CVE-2026-96820
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-30. A secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 7.1
- EG Score
- 7.1HIGHhigh confidence
- EG Risk
- 32EG Risk 32/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.2%
- EPSS %ILE
- 13th
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 30, 2026
Last Modified
September 30, 2026
References (1)
Vendor Advisories for CVE-2026-96820(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-04 17:23 UTCGHSA enrichment
- 2026-10-04 06:28 UTCGHSA enrichment
- 2026-10-03 19:35 UTCEG score recompute
- 2026-10-03 19:35 UTCGHSA enrichment
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 08:42 UTCGHSA enrichment
- 2026-10-02 21:48 UTCEG score recompute
- 2026-10-02 21:48 UTCGHSA enrichment
- 2026-10-02 17:57 UTCEPSS rescore
- 2026-10-02 10:54 UTCGHSA enrichment
- 2026-10-02 00:01 UTCEG score recompute
- 2026-10-02 00:01 UTCGHSA enrichment
- 2026-10-01 19:51 UTCEPSS rescore
- 2026-10-01 12:13 UTCGHSA enrichment
- 2026-10-01 01:21 UTCEG score recompute
- 2026-10-01 01:21 UTCGHSA enrichment
- 2026-09-30 14:18 UTCEG score recompute
- 2026-09-30 13:34 UTCEG score recompute
- 2026-09-30 13:21 UTCEG score recompute
- 2026-09-30 12:54 UTCEG score recompute
- 2026-09-30 12:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-96820?
When was CVE-2026-96820 disclosed?
Is CVE-2026-96820 actively exploited?
What is the CVSS score of CVE-2026-96820?
How do I remediate CVE-2026-96820?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-96820
Is Your Infrastructure Affected by CVE-2026-96820?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.