Skip to main content
VulnerabilityPublished Updated

CVE-2025-70365: kiamo · Cross-site Scripting

Affects kiamoSource CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium : upgrade to 8.4 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade kiamo/kiamo to 8.4.

Affected software

ProductAffectedFixed in
GitHubkiamo/kiamopkg:github/kiamo/kiamoOther threatsAffected
  • <8.4
Fixed in
  • 8.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available and was released in Kiamo version 8.3.1. Users should upgrade to version 8.3.1 or later to remediate this vulnerability. No additional mitigation steps are indicated by the supplier.

Description

A 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.

References

Community reviews

Loading reviews…