Is CVE-2026-63107 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63107 being exploited in the wild.

How severe is CVE-2026-63107?

High severity, with a CVSS score of 7.7, published 20 July 2026.

Which products and versions are affected?

LimeSurvey <= 6.17.10, <= 7.0.4.

Is there a fix for CVE-2026-63107?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-63107 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-63107?

Check whether you run LimeSurvey at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63107: LimeSurvey SSRF in REST API survey template endpoint

Q: Which products and versions are affected?

LimeSurvey <= 6.17.10, <= 7.0.4.

Q: Is there a fix for CVE-2026-63107?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-63107 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-63107?

Check whether you run LimeSurvey at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63107 · Severity: high · CVSS 7.7 · Published 2026-07-20

LimeSurvey, a popular open-source survey tool, contains a security flaw in its programming interface (API) used for managing survey templates. An authorized user can trick the server into making unauthorized connections to internal systems or cloud management services. This could allow an attacker to steal sensitive data, such as cloud access tokens or information from other private servers, that are not normally accessible from the internet.

Technologies: LimeSurvey. Vendors: LimeSurvey.

Quick answers

Is CVE-2026-63107 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63107 being exploited in the wild.
How severe is CVE-2026-63107?: High severity, with a CVSS score of 7.7, published 20 July 2026.
Which products and versions are affected?: LimeSurvey <= 6.17.10, <= 7.0.4.
Is there a fix for CVE-2026-63107?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-63107 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-63107?: Check whether you run LimeSurvey at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in the `getTemplateData()` function within `application/libraries/Api/Command/V1/SurveyTemplate.php`. The application unsafely uses the HTTP 'Host' header to construct a URL for a server-side cURL request intended to render survey previews. An authenticated attacker with survey 'read' permissions can manipulate the Host header to force the server to perform GET requests against arbitrary internal or external targets. Because the application disables TLS verification (CURLOPT_SSL_VERIFYPEER/HOST) and returns the full response body, attackers can exfiltrate sensitive data from internal services or cloud metadata endpoints (e.g., IMDSv2).

Affected products

LimeSurvey LimeSurvey <= 6.17.10, <= 7.0.4

Timeline

2026-07-20: disclosed
2026-07-20: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.