CVE-2025-11188
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 blind SQL injection in the nas-id parameter, allowing for SQL commands to be issued and to compromise the corresponding database.
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 contains a blind SQL injection vulnerability in the nas-id parameter. The flaw allows attackers to inject malicious SQL commands through this input field, potentially enabling unauthorized database access, data exfiltration, or full database compromise. As a blind SQL injection, the attacker infers true/false conditions from application response differences rather than seeing direct database output.
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 installation existsLocate Kiwire Captive Portal installation by checking for its web application files, service, or documentation. Common paths may include /var/www/kiwire or C:\Program Files\kiwire on Windows servers.Affected if Kiwire Captive Portal software is not installed in the environment
-
Identify installed Kiwire versionAccess the Kiwire admin interface or check version files within the installation directory. Look for a version file or system information page that displays the installed software version.Affected if The installed version is exactly 3.6 (the only affected version per the CVE)
-
Verify captive portal functionality is enabledCheck the Kiwire configuration to confirm the captive portal feature is active. This may be in the admin panel under network settings, hotspot configuration, or captive portal settings.Affected if The captive portal feature is enabled and accessible to users
-
Confirm nas-id parameter is accessibleTest access to the captive portal login or splash page and inspect the HTML forms or URL parameters for a nas-id field. This parameter is typically used in NAS (Network Access Server) identification for hotspot authentication.Affected if The nas-id parameter is present in the captive portal interface and accepts user input
The environment is affected only if Kiwire version 3.6 is installed AND the captive portal with the nas-id parameter is enabled and accessible.
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 parameterized queries or prepared statements for all database interactions involving the nas-id parameter. Additionally, apply strict input validation and enforce least-privilege database account access to limit the impact of any successful injection.
- Consultation4.0 h
- Implementation10.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11188 — 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-11188 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