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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

0.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:N

EPSS

• CVE-2026-55630: 0.42% estimated exploitation activity in the next 30 days; percentile 36.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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

Published by the source

6 Jul 2026, 21:49 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:46 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-473p-56xx-vg67

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-473p-56xx-vg67

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55630

Advisory: Kiwi TCMS vulnerable to stored XSS via JavaScript: URI in extra_link field (TestPlan & TestCase)
IDs: CVE-2026-55630, GHSA-473p-56xx-vg67
Record: https://patchnext.com/advisories/cve-2026-55630 (revision 2, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated (CVSS 0.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI kiwitcms: affected <= 12.4

## Suggested inspection (read-only)
- `python -m pip show kiwitcms`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on kiwitcms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-473p-56xx-vg67 (OSV record GHSA-473p-56xx-vg67 lists affected ranges: PyPI kiwitcms >=0 <=12.4)
- Verified: https://github.com/advisories/GHSA-473p-56xx-vg67 (GitHub-reviewed advisory GHSA-473p-56xx-vg67 lists affected ranges: PyPI kiwitcms >=0 <=12.4)

Commands are suggestions: review each one before running it.