CVE-2025-70365
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 · uneditedA stored cross-site scripting (XSS) vulnerability exists in Kiamo before 8.4 due to improper output encoding of user-supplied input in administrative interfaces. An authenticated administrative user can inject arbitrary JavaScript code that is executed in the browser of users viewing the affected pages. NOTE: the Supplier's position is that a fix for this had already been released for the 8.3.1 branch before the CVE Record was published.
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 · high confidenceA stored cross-site scripting (XSS) vulnerability in Kiamo's administrative interfaces allows authenticated admin users to inject malicious JavaScript through user-supplied input that is not properly output-encoded. When other users view the affected admin pages, the injected script executes in their browsers, potentially enabling session hijacking or credential theft.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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.
-
Verify Kiamo installation existsCheck for Kiamo installation directories (common paths: /opt/kiamo, C:\Kiamo, or /var/www/kiamo) or look for kiamo service/process running on the systemAffected if Kiamo software is not found on the system
-
Determine installed Kiamo versionLocate version information in installation files such as version.info, about.php, or run: kiamo --version, or check the web interface /about pageAffected if Version cannot be determined or is earlier than 8.4
-
Confirm admin interface is accessibleVerify the administrative web interface is reachable at typical paths like /admin, /kiamo-admin, or the configured admin URL. Check that admin user accounts exist.Affected if Admin interface is not accessible or no admin users are configured
-
Identify admin input fieldsNavigate to admin interface sections that accept user input such as user management, configuration forms, or notification settings. Common vulnerable areas include text fields for names, descriptions, or custom messages.Affected if No input fields are present in the admin interface
-
Compare version to affected rangeCompare your installed version against the affected range: versions prior to 8.4, or versions 8.3.0-8.3.1 without the supplier patch appliedAffected if Installed version is 8.3.x without patch or any version earlier than 8.3.x
You are affected if running Kiamo version 8.3.x without the supplier patch or any version earlier than 8.3.x, and your admin interface with input fields is accessible to authenticated administrators.
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 dataUpgrade to Kiamo version 8.4 or later (or apply the supplier's 8.3.1 patch if not already applied). Conduct a thorough audit of all administrative interface input fields to ensure consistent output encoding across the application.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-70365 — 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-70365 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