CVE-2026-55630

LOWCVSS · not yet scored
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: CVSS v2: Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Kiwi TCMS vulnerable to stored XSS via JavaScript: URI in extra_link field (TestPlan & TestCase)

Summary

In Kiwi TCMS the fields TestCase.extra_link and TestPlan.extra_link were meant to represent URLs to external resources however in versions prior to 16.1 user input was not being sanitized and values were rendered verbatim which represents an opportunity for cross-site scripting exploitation. In version 16.1 these fields are properly sanitized and existing database records which don't validate will be reset to a null value.

Impact

Deployments which use the official Docker images and/or unmodified Kiwi TCMS middleware send a Content-Security-Policy header which makes this vulnerability difficult to exploit in practice because this header blocks the browser from executing inline JavaScript. Customized deployments which modify the default security settings may still be vulnerable.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
EPSS %ILE
KEV
Not listed

Published

July 6, 2026

Last Modified

July 6, 2026

Vendor Advisories for CVE-2026-55630(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipkiwitcmsghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
kiwitcms10.0 ... 9.999 (49 versions)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 12:06 UTCGHSA enrichment
  2. 2026-08-22 12:22 UTCGHSA enrichment
  3. 2026-08-19 12:30 UTCGHSA enrichment
  4. 2026-08-16 12:34 UTCGHSA enrichment
  5. 2026-08-13 12:52 UTCGHSA enrichment
  6. 2026-08-10 13:10 UTCGHSA enrichment
  7. 2026-08-07 13:28 UTCGHSA enrichment
  8. 2026-08-04 13:47 UTCGHSA enrichment
  9. 2026-08-01 12:10 UTCEG score recompute
  10. 2026-08-01 12:10 UTCGHSA enrichment
  11. 2026-07-29 12:27 UTCGHSA enrichment
  12. 2026-07-26 12:45 UTCEG score recompute
  13. 2026-07-26 12:45 UTCGHSA enrichment
  14. 2026-07-23 03:20 UTCEG score recompute
  15. 2026-07-15 21:43 UTCGHSA enrichment
  16. 2026-07-12 22:01 UTCGHSA enrichment
  17. 2026-07-09 22:19 UTCGHSA enrichment
  18. 2026-07-06 22:35 UTCEG score recompute
  19. 2026-07-06 22:35 UTCGHSA enrichment

Frequently asked(3)

What is CVE-2026-55630?
CVE-2026-55630 is a low vulnerability published on July 6, 2026. Kiwi TCMS vulnerable to stored XSS via JavaScript: URI in extra_link field (TestPlan & TestCase) Summary In Kiwi TCMS the fields TestCase.extralink and TestPlan.extralink were meant to represent URLs to external resources however in versions prior to 16.1 user input was not being sanitized and…
When was CVE-2026-55630 disclosed?
CVE-2026-55630 was first published in the National Vulnerability Database on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
How do I remediate CVE-2026-55630?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55630, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55630

Explore →

Is Your Infrastructure Affected by CVE-2026-55630?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.