Kiwi TCMS Stored Cross-site Scripting via SVG file

Exploitation

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

CVSS

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

EPSS

• CVE-2023-27489: 0.48% estimated exploitation activity in the next 30 days; percentile 41.78 (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.

Impact Kiwi TCMS accepts SVG files uploaded by users which could potentially contain JavaScript code. If SVG images are viewed directly, i.e. not rendered in an HTML page, this JavaScript code could execute. Patches This vulnerability has been fixed by configuring Kiwi TCMS to serve with the Content-Security-Policy HTTP header which blocks inline JavaScript in all modern browsers. Workarounds Configure Content-Security-Policy header, see commit 6617cee0. References You can visit https://digi.ninja/blog/svgxss.php for more technical details. Independently disclosed by Antonio Spataro and @1d8.

Published by the source

30 Mar 2023, 20:18 UTC

Last modified by the source

10 Sep 2026, 03:49 UTC

Source last checked

26 Oct 2026, 13:11 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2wcr-87wf-cf9j

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-2wcr-87wf-cf9j

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

# Patch Next advisory brief: CVE-2023-27489

Advisory: Kiwi TCMS Stored Cross-site Scripting via SVG file
IDs: CVE-2023-27489, GHSA-2wcr-87wf-cf9j
Record: https://patchnext.com/advisories/cve-2023-27489 (revision 2, source checked 26 Oct 2026, 13:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: kiwitcms 12.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI kiwitcms: affected < 12.1; fixed in 12.1

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## 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-2wcr-87wf-cf9j (OSV record GHSA-2wcr-87wf-cf9j lists affected ranges: PyPI kiwitcms >=0 <12.1 (fixed))
- Verified: https://github.com/advisories/GHSA-2wcr-87wf-cf9j (GitHub-reviewed advisory GHSA-2wcr-87wf-cf9j lists affected ranges: PyPI kiwitcms >=0 <12.1)

Commands are suggestions: review each one before running it.