Kiwi TCMS's misconfigured HTTP headers allow stored XSS execution with Firefox

Exploitation

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

CVSS

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

EPSS

• CVE-2023-36809: 0.69% estimated exploitation activity in the next 30 days; percentile 52.94 (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 allows users to upload attachments to test plans, test cases, etc. Earlier versions of Kiwi TCMS had introduced changes which were meant to serve all uploaded files as plain text in order to prevent browsers from executing potentially dangerous files when such files are accessed directly! The previous Nginx configuration was incorrect allowing certain browsers like Firefox to ignore the Content-Type: text/plain header on some occasions thus allowing potentially dangerous scripts to be executed. Additionally file upload validators and parts of the HTML rendering code have been found to require additional sanitation and improvements. Patches - Updated Nginx content type configuration - Improved file upload validation code to prevent more potentially dangerous uploads - Sanitization of test plan names used in the treeviewhtml() function References Disclosed by M Nadeem Qazi and Mahshooq Zubair.

Published by the source

5 Jul 2023, 22:40 UTC

Last modified by the source

7 Jul 2026, 17:56 UTC

Source last checked

26 Oct 2026, 13:12 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jpgw-2r9m-8qfw

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jpgw-2r9m-8qfw

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

# Patch Next advisory brief: CVE-2023-36809

Advisory: Kiwi TCMS's misconfigured HTTP headers allow stored XSS execution with Firefox
IDs: CVE-2023-36809, GHSA-jpgw-2r9m-8qfw
Record: https://patchnext.com/advisories/cve-2023-36809 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: kiwitcms 12.5. A vendor fix does not mean a deployment is fixed.

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

## 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-jpgw-2r9m-8qfw (OSV record GHSA-jpgw-2r9m-8qfw lists affected ranges: PyPI kiwitcms >=0 <12.5 (fixed))
- Verified: https://github.com/advisories/GHSA-jpgw-2r9m-8qfw (GitHub-reviewed advisory GHSA-jpgw-2r9m-8qfw lists affected ranges: PyPI kiwitcms >=0 <12.5)

Commands are suggestions: review each one before running it.