CVE-2026-63107

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

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

Score 7.7 from GitHub Security Advisory published 2026-07-20. The CNA's CVSS baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-46061 (ENISA EUVD) · GHSA-34qp-wv4h-827h (GitHub Security Advisories)Source: ENISA EUVD

7.7EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (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.4%CVSS: 7.7Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists LimeSurvey versions up to and including 6.17.10 and up to and including 7.0.4 as affected. No release containing a fix is confirmed on record.

LimeSurvey through 6.17.10 and 7.0.4 contains a server-side request forgery vulnerability in the REST API survey template endpoint that allows authenticated users to cause the server to issue arbitrary HTTP requests by supplying a manipulated Host header. Attackers can exploit the unsanitized use of the HTTP Host header in the getTemplateData() function to reach internal network services, cloud metadata endpoints, and extract sensitive credentials such as IAM tokens from instance metadata services.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
51
EG Risk 51/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)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.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: 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.4%
EPSS %ILE
28th
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 (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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.Each input and its source: 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).

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 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.

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

July 20, 2026

Last Modified

July 28, 2026

Advisory Details (2)

Auto-updated Jul 20, 2026
No fix on record yet.
Web page

LimeSurvey SSRF via REST API Survey Template Host Header | Advisories | VulnCheck

https://www.vulncheck.com/advisories/limesurvey-ssrf-via-rest-api-survey-template-host-header
Web page

oss/limesurvey.md at main · geo-chen/oss · GitHub

https://github.com/geo-chen/oss/blob/main/limesurvey.md

Vendor Advisories for CVE-2026-63107(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 10× in last 7d / 45× 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 240 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 140 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-63107?
CVE-2026-63107 is a high-severity vulnerability; its CVE record was published on July 20, 2026. LimeSurvey through 6.17.10 and 7.0.4 contains a server-side request forgery vulnerability in the REST API survey template endpoint that allows authenticated users to cause the server to issue arbitrary HTTP requests by supplying a manipulated Host header. Attackers can exploit the unsanitized use…
When was CVE-2026-63107 made public?
CVE-2026-63107 was made public on June 30, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 20, 2026. EchelonGraph's copy of the record carries a last-modified date of July 28, 2026; the record at its source may have been updated since.
Is CVE-2026-63107 actively exploited?
CVE-2026-63107 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63107?
CVE-2026-63107 has a CVSS base score of 7.7 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-63107?
No fix for CVE-2026-63107 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists LimeSurvey versions up to and including 6.17.10 and up to and including 7.0.4 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-63107 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63107

Explore →

Is Your Infrastructure Affected by CVE-2026-63107?

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