CVE-2025-11360VulnerabilityPublished 7 Oct 2025

CVE-2025-11360: jakowenko double-take · Cross Site Scripting

Affects jakowenko double-takeSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
jakowenko double-take	Affected =1.13.0 =1.13.1	Fixed in–

AI-suggested

The definitive mitigation is to upgrade jakowenko double-take to version 1.13.2 or later, which contains the official patch addressing the XSS vulnerability. Organizations should audit their deployments to identify any instances running affected versions 1.13.0 or 1.13.1 and prioritize patching. Additionally, implementing strict input validation and sanitization on HTTP headers, especially X-Ingress-Path, can reduce risk. Web application firewalls (WAFs) should be configured to detect and block suspicious header manipulations. Security teams should also educate users about the risks of interacting with untrusted links or content that could trigger XSS attacks. Monitoring logs for anomalous header values and unusual user activity can help detect exploitation attempts. Finally, adopting Content Security Policy (CSP) headers can mitigate the impact of XSS by restricting script execution contexts.

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.

Impact

For European organizations, the primary impact of CVE-2025-11360 lies in the potential compromise of user data and session integrity through client-side script injection. This could lead to theft of sensitive information, unauthorized actions performed in the context of authenticated users, and reputational damage if exploited. Organizations relying on jakowenko double-take for API services or web applications may face increased risk of targeted attacks, especially if their user base includes high-value or sensitive profiles. The vulnerability could be leveraged in spear-phishing campaigns or combined with other attack vectors to escalate privileges or move laterally within networks. Given the medium severity and the requirement for user interaction, the risk is moderate but non-negligible, particularly for sectors with stringent data protection requirements such as finance, healthcare, and government. Failure to patch could also result in non-compliance with GDPR mandates on data security and breach prevention.

Summary

CVE-2025-11360 is a cross-site scripting vulnerability identified in the jakowenko double-take product, specifically affecting versions 1.13.0 and 1.13.1. The vulnerability arises from improper sanitization of the X-Ingress-Path HTTP header within the API component's app.use function located in api/src/app.js. This flaw allows an attacker to craft a malicious X-Ingress-Path header that injects executable script code into the web application's response. Since the attack vector is remote and does not require authentication, any user accessing the vulnerable application with a manipulated header could execute arbitrary JavaScript in their browser context. The vulnerability impacts the confidentiality and integrity of user sessions by enabling theft of cookies, session tokens, or performing actions on behalf of the user. The CVSS 4.0 base score is 5.3 (medium severity), reflecting the ease of exploitation (no privileges or authentication needed) but requiring user interaction to trigger the payload. The vulnerability is resolved by upgrading to version 1.13.2, which includes a patch identified by commit e11de9dd6b4ea6b7ec9a5607a920d48961e9fa50. No public exploits have been reported yet, but the presence of this vulnerability in an API component suggests potential for targeted phishing or social engineering attacks leveraging the XSS flaw.

References

Community reviews

Loading reviews…