CVE-2025-11189: Synchroweb Kiwire · Cross-site Scripting
Affects Synchroweb KiwireSource CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 10 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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Synchroweb Kiwire | Affected
| Fixed in– |
AI-suggested
1. Immediate monitoring for any suspicious activity involving the login-url parameter in Kiwire captive portals. 2. Implement strict input validation and sanitization on the login-url parameter to neutralize any injected scripts, using allowlists and encoding techniques. 3. Deploy or update Web Application Firewalls (WAFs) with rules specifically targeting reflected XSS patterns related to captive portal URLs. 4. Restrict or sanitize URL parameters at the network edge or proxy level to prevent malicious payloads from reaching the captive portal. 5. Educate users and administrators about the risks of clicking on suspicious links related to captive portals. 6. Coordinate with Synchroweb for timely patch releases and apply updates as soon as they become available. 7. Conduct regular security assessments and penetration testing focused on captive portal components to identify and remediate similar vulnerabilities. 8. Consider implementing Content Security Policy (CSP) headers to limit the execution of unauthorized scripts within captive portal pages.
Description
The Kiwire Captive Portal contains a reflected cross-site scripting (XSS) vulnerability within the login-url parameter, allowing for Javascript execution.