CVE-2026-25383
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Iqonic Design KiviCare kivicare-clinic-management-system allows Reflected XSS.This issue affects KiviCare: from n/a through <= 3.6.16.
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 confidenceReflected XSS vulnerability in KiviCare clinic management system where user-supplied input is not properly sanitized before being rendered in web pages, allowing attackers to inject malicious scripts that execute in victims' browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Identify KiviCare installation versionLog into the KiviCare admin dashboard and navigate to Settings > About, or inspect the root directory for a version file (such as readme.txt, composer.json, or a config file that stores the application version)Affected if The installed version is lower than 3.6.17 and the application reflects user-supplied input in web pages without sanitization
-
Verify user input reflection in browserNavigate to a page in KiviCare that accepts user input (such as search, forms, or URL parameters), and inject a test payload like <script>alert('XSS')</script> into input fields or URL parametersAffected if The injected script executes or appears in the page source unescaped, indicating lack of output encoding
-
Inspect HTTP responses for unsanitized parametersUse browser developer tools or a proxy (Burp Suite, ZAP) to intercept requests and responses. Submit requests with special characters in parameters and examine if they are returned verbatim in the response HTMLAffected if User-supplied values are returned in the response body without HTML entity encoding (e.g., < appears as < rather than <)
-
Check application configuration for security settingsExamine KiviCare configuration files for any XSS protection settings,Content-Security-Policy headers, or input validation configurationsAffected if No output encoding or input validation is configured, and the version is below 3.6.17
-
Review vulnerable endpoint parametersIdentify KiviCare endpoints that accept user input via GET or POST parameters (such as patient search, appointment booking, or form submissions) and test each parameter for XSSAffected if Any parameter reflects input without sanitization, indicating the system is affected by this reflected XSS vulnerability
The environment is affected if KiviCare version is below 3.6.17 AND user-supplied input is reflected in web pages without proper HTML entity encoding.
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 output encoding and input validation/sanitization on all user-controlled parameters before rendering them in HTML context. Upgrade to version 3.6.17 or later if available.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25383 — 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-2026-25383 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