CVE-2024-47947

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 4.7 from GitHub Security Advisory published 2024-12-12. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2024-42843 (ENISA EUVD) · GHSA-f9hr-3m6x-jmr5 (GitHub Security Advisories)Source: ENISA EUVD

4.7EG
EchelonGraph verdictPlan mitigationNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 4.7Exploit: No code on recordExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Due to missing input sanitization, an attacker can perform cross-site-scripting attacks and run arbitrary Javascript in the browser of other users. The "Edit Disclaimer Text" function of the configuration menu is vulnerable to stored XSS. Only the users Poweruser and Admin can use this function which is available at the URL

https://$SCANNER/cgi/admin.cgi?-rdisclaimer+-apre

The stored Javascript payload will be executed every time the ScanWizard is loaded, even in the Kiosk-mode browser.

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
37
EG Risk 37/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)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.5%
EPSS %ILE
41st
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 (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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 or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

December 12, 2024

Last Modified

April 15, 2026

References (3)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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 95 of 221 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 126 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-25 17:00 UTCEG score recompute
  9. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-24 04:27 UTCEG score recompute
  12. 2026-10-24 04:27 UTCGHSA enrichmentGHSA-f9hr-3m6x-jmr5 · GitHub CVSS 4.7
  13. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-18 06:57 UTCEG score recompute
  20. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-10-12 17:43 UTCEG score recompute
Show 70 more
  1. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-11 21:08 UTCEG score recompute
  3. 2026-10-11 16:00 UTCEG score recompute
  4. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-09-30 19:55 UTCEG score recompute
  15. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-09-17 19:27 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  26. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  27. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  28. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  29. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  30. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  31. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  32. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  33. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  34. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  35. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  36. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  37. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  38. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  39. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  40. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  41. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  42. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  43. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  44. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  45. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  46. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  47. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  48. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  49. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  50. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  51. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  52. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  53. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  54. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  55. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  56. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  57. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  58. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  59. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  60. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  61. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  62. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  63. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  64. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  65. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  66. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  67. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  68. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  69. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  70. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.5% · 38th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-47947?
CVE-2024-47947 is a medium-severity vulnerability; its CVE record was published on December 12, 2024. Due to missing input sanitization, an attacker can perform cross-site-scripting attacks and run arbitrary Javascript in the browser of other users. The "Edit Disclaimer Text" function of the configuration menu is vulnerable to stored XSS. Only the users Poweruser and Admin can use this function…
When was the CVE record for CVE-2024-47947 published?
The CVE record for CVE-2024-47947 was published on December 12, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-47947 actively exploited?
CVE-2024-47947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-47947?
CVE-2024-47947 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2024-47947?
A fix for CVE-2024-47947 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-47947

Explore →

Is Your Infrastructure Affected by CVE-2024-47947?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs