SkillTree is a micro-learning gamification platform. Prior to version 4.4.2, two independent code flaws combine into a single exploitable attack chain, with three distinct exploitation paths of escalating impact. StringHighlighter.js builds an HTML string by interpolating raw value substrings directly into a template literal with no HTML entity encoding. HighlightedValue.vue renders that string — and all unfiltered plain values — via Vue's v-html directive, which sets innerHTML. Separately, the account registration endpoint accepts firstName, lastName, and nickname fields and stores them without any HTML sanitization. An attacker self-registers with firstName = "" (28 characters — within the 30-character field limit) and visits any quiz. The next time an administrator opens the Quiz Runs page the payload executes in their browser. Three attack paths exist with escalating impact. The first is basic cross-site scripting. Any self-contained payload fitting the 30-character limit (e.g. `, which is 28 chars) fires automatically when the admin navigates to the runs page through normal use. Arbitrary code execution in the admin's browser is confirmed with zero extra steps. The second is remote script loading via import(). Using the split-field technique (lastName = ""), the attacker loads a full JavaScript file from their server. The file has no size limit and can perform any admin action — delete all projects, create backdoor accounts, dump user data, install a keylogger. No phishing required. The only constraint is that the URL must fit in 11 characters (//nsas.cc/p). The third is full cross-site request forgery token theft. Using eval(name), the attacker pre-sets window.name to a data-theft payload by sending the admin one redirect link first. The session cookie is HttpOnly and cannot be read via document.cookie`; however, the XSRF token is readable and the attacker leverages same-origin execution to call admin APIs from inside the victim's browser, relaying the responses to an external server. No admin interaction beyond routine use is required. Version 4.4.2 contains a patch.
CVE-2026-54694
“—” beside the score: it is equal to the CVSS score beside it.
This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-75116 (ENISA EUVD)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
The CVE record names the fixed release — apply it.
- CVSS v3
- 9.6
- EG Score
- 9.6CRITICALmedium confidence
- EG Risk
- 59EG Risk 59/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity96% × 45%Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.5%
- EPSS %ILE
- 40th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 9, 2026
Last Modified
September 10, 2026
Advisory Details (1)
Auto-updated Oct 7, 2026Stored XSS in NationalSecurityAgency/skills-service via User Registration Enabling Admin Account Takeover · Advisory · NationalSecurityAgency/skills-service · GitHub
https://github.com/NationalSecurityAgency/skills-service/security/advisories/GHSA-hqfg-c8wf-w2g8Weakness Classification(5)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 64× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 111 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 11 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 01:15 UTCEG score recompute
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-11-01 03:21 UTCEG score recompute
- 2026-10-31 05:28 UTCEG score recompute
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-30 07:35 UTCEG score recompute
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-29 09:43 UTCEG score recompute
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-28 11:50 UTCEG score recompute
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-27 13:51 UTCEG score recompute
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-25 16:50 UTCEG score recompute
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-25 14:19 UTCEG score recompute
- 2026-10-24 18:57 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-23 21:05 UTCEG score recompute
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-22 23:12 UTCEG score recompute
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-22 01:19 UTCEG score recompute
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-21 03:22 UTCEG score recompute
Show 75 moreShow fewer
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-20 05:28 UTCEG score recompute
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-19 06:54 UTCEG score recompute
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-18 03:30 UTCEG score recompute
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-17 06:14 UTCEG score recompute
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-16 07:22 UTCEG score recompute
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-15 06:17 UTCEG score recompute
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-14 01:57 UTCEG score recompute
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-12 22:14 UTCEG score recompute
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-12 15:56 UTCEG score recompute
- 2026-10-11 19:39 UTCEG score recompute
- 2026-10-11 16:54 UTCEG score recompute
- 2026-10-11 14:17 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-11 11:52 UTCEG score recompute
- 2026-10-10 20:12 UTCEG score recompute
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-09 23:55 UTCEG score recompute
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-08 23:57 UTCEG score recompute
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-07 23:50 UTCEG score recompute
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-06 16:03 UTCEG score recompute
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-05 20:24 UTCEG score recompute
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-04 23:24 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-03 19:09 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-02 21:20 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-01 21:20 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-30 18:21 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-30 02:01 UTCEG score recompute
- 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-28 22:32 UTCEG score recompute
- 2026-09-28 18:43 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-27 14:43 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-26 19:12 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-26 01:28 UTCEG score recompute
- 2026-09-24 14:44 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-23 19:36 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-09-22 16:07 UTCEG score recompute
- 2026-09-22 00:45 UTCEG score recompute
- 2026-09-20 21:10 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-09-19 18:23 UTCEG score recompute
- 2026-09-18 23:07 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-09-17 20:14 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-09-16 14:39 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-09-16 06:58 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-09-15 03:43 UTCEG score recompute
- 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-09-13 17:16 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-20 · CWE-116 · CWE-79
Frequently asked(5)
What is CVE-2026-54694?
When was the CVE record for CVE-2026-54694 published?
Is CVE-2026-54694 actively exploited?
What is the CVSS score of CVE-2026-54694?
How do I remediate CVE-2026-54694?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54694
Is Your Infrastructure Affected by CVE-2026-54694?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.