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.
CVE-2026-63107
Score 7.7 from GitHub Security Advisory published 2026-07-20. a secondary CVSS source baseline 7.7; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.7
- EG Score
- 7.7(high)
- EG Risk
- 51(Track)EG Risk 51/100SSVC: Track
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 computedSeverity77% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
July 20, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jul 20, 2026LimeSurvey SSRF via REST API Survey Template Host Header | Advisories | VulnCheck
https://www.vulncheck.com/advisories/limesurvey-ssrf-via-rest-api-survey-template-host-headeross/limesurvey.md at main · geo-chen/oss · GitHub
https://github.com/geo-chen/oss/blob/main/limesurvey.mdVendor 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 19× in last 7d / 19× 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-07-27 03:14 UTCGHSA enrichment
- 2026-07-26 15:50 UTCEG score recompute
- 2026-07-26 15:50 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 04:28 UTCEG score recompute
- 2026-07-26 04:28 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 20:43 UTCEG score recompute
- 2026-07-20 18:37 UTCEG score recompute
- 2026-07-20 18:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-14721EG 10.0EPSS p95CRITICAL
- CVE-2018-18843EG 10.0CRITICAL
- CVE-2018-19047EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-3774EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2018-1789NVD 8.4EG 9.9CRITICAL
Frequently asked(5)
What is CVE-2026-63107?
When was CVE-2026-63107 disclosed?
Is CVE-2026-63107 actively exploited?
What is the CVSS score of CVE-2026-63107?
How do I remediate CVE-2026-63107?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63107
Is Your Infrastructure Affected by CVE-2026-63107?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.