CVE-2025-11189
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Kiwire Captive Portal contains a reflected cross-site scripting (XSS) vulnerability within the login-url parameter, allowing for Javascript execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceKiwire Captive Portal has a reflected XSS vulnerability in the login-url parameter. User-supplied input in this parameter is not properly sanitized before being rendered in the response, allowing an attacker to inject malicious JavaScript that executes in the victim's browser.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Kiwire Captive Portal installationLocate the Kiwire installation directory or identify the web service hosting the captive portal. Common locations include /var/www/kiwire or C:\Program Files\Kiwire. Check for kiwire-related processes or services running on the system.Affected if Kiwire Captive Portal is not installed on the system.
-
Identify installed Kiwire versionCheck the Kiwire version by inspecting version files, about pages, or running version commands within the Kiwire management interface. Compare the discovered version against the affected range: version 3.6.Affected if The installed version is exactly 3.6.
-
Verify login-url parameter is accessibleAccess the captive portal login page and examine the HTTP requests/responses. Look for the login-url parameter in the request URL or form submission. Inspect the HTML source of the login page to see if login-url values are reflected in the response.Affected if The login-url parameter exists and user-supplied values are reflected in the response without encoding.
-
Inspect input handling for login-urlReview the Kiwire configuration files or web application source code for how the login-url parameter is handled. Check if the parameter value is used directly in HTML output or if output encoding is applied.Affected if The login-url parameter is used directly in responses without sanitization or encoding.
The system is affected if Kiwire Captive Portal version 3.6 is installed and the login-url parameter reflects user input without proper sanitization in the HTTP response.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper input validation and output encoding for the login-url parameter. Use a whitelist approach for valid URLs and ensure all user input is escaped before being included in HTML output.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11189 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11189 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data