CVE-2025-11190
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 an open redirection issue via the login-url parameter, allowing an attacker to redirect users to an attacker controlled website.
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 an open redirection vulnerability in the login-url parameter. Attackers can craft malicious URLs that redirect authenticated users to attacker-controlled websites, enabling phishing and credential theft attacks.
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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
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.
-
Identify installed Kiwire versionLocate the Kiwire installation and determine the exact software version number. Check system information, about page, or version file within the Kiwire application directory.Affected if The installed version is exactly 3.6, as this is the only version confirmed affected by CVE-2025-11190.
-
Confirm Captive Portal module is activeVerify that the Captive Portal feature is enabled and accessible on the Kiwire deployment. This may be confirmed through the admin interface, network configuration, or by attempting to access the captive portal login page.Affected if The Captive Portal is enabled and reachable, exposing the login-url parameter to user interaction.
-
Locate the login-url parameterExamine the Captive Portal login page or its form submission handling to identify the login-url parameter. This parameter typically controls the post-login redirect destination.Affected if The login-url parameter exists and accepts user-supplied input without strict validation.
-
Inspect redirect URL validation logicReview the server-side code or configuration that processes the login-url parameter to determine whether URL validation is implemented. Look for allowlist enforcement or restriction to relative URLs.Affected if No allowlist-based URL validation exists, or the validation allows arbitrary external domains in the login-url parameter.
A user is affected if they run Synchroweb Kiwire version 3.6 with the Captive Portal enabled and the login-url parameter accepts unvalidated external URLs.
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 strict URL validation on the login-url parameter, restricting redirects to an allowlist of trusted domains or requiring relative URLs only.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11190 — 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-11190 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