# CVE-2025-11360: jakowenko double-take API app.js app.use cross site scripting


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Oct 2025
- **Updated:** 7 Oct 2025
- **Also known as:** GHSA-q9xj-4j4j-jcwh

## What is CVE-2025-11360?

CVE-2025-11360 is a medium-severity vulnerability in jakowenko double-take, published on 7 Oct 2025. 

### Official description

A vulnerability was detected in jakowenko double-take up to 1.13.1. The impacted element is the function app.use of the file api/src/app.js of the component API. The manipulation of the argument X-Ingress-Path results in cross site scripting. The attack can be executed remotely. Upgrading to version 1.13.2 is sufficient to resolve this issue. The patch is identified as e11de9dd6b4ea6b7ec9a5607a920d48961e9fa50. The affected component should be upgraded.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-11360?


## How do I fix CVE-2025-11360?

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

## Is CVE-2025-11360 being exploited?

There is no known exploitation of CVE-2025-11360 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11360 and fix it if it is affected.

What it is: CVE-2025-11360 is a medium-severity vulnerability in jakowenko double-take, published on 7 Oct 2025. 
Exploitation: There is no known exploitation of CVE-2025-11360 in the wild and no public exploit code.

Affected product: jakowenko double-take. 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-2025-11360/ (Markdown: https://insights.sbomify.com/CVE-2025-11360/index.md)
```

## Sources

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

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