# CVE-2026-63107: LimeSurvey SSRF via REST API Survey Template Host Header

> Authenticated attackers can exploit an SSRF vulnerability in LimeSurvey's REST API to access internal services and steal cloud credentials via manipulated Host headers.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-34qp-wv4h-827h

## What is CVE-2026-63107?

CVE-2026-63107 is a medium-severity server-side request forgery vulnerability in LimeSurvey, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-63107?


## How do I fix CVE-2026-63107?

No fix has been published for CVE-2026-63107 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63107 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63107 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63107 and fix it if it is affected.

What it is: CVE-2026-63107 is a medium-severity server-side request forgery vulnerability in LimeSurvey, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63107 exists.

Affected product: LimeSurvey. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63107/ (Markdown: https://insights.sbomify.com/CVE-2026-63107/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63107
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63107
- OSV: https://osv.dev/vulnerability/CVE-2026-63107

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63107/
Summaries are generated and may contain mistakes; the official description above is the record.