kiwitcms vulnerable to stored XSS via unrestricted files upload
CVE-2023-32686GHSA-x7c2-7wvg-jpx7
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (kiwitcms 12.3), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI kiwitcms
- Affected
- < 12.3
- Fixed in
- 12.3
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-x7c2-7wvg-jpx7 lists affected ranges: PyPI kiwitcms >=0 <12.3 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-x7c2-7wvg-jpx7 lists affected ranges: PyPI kiwitcms >=0 <12.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
- EPSS
- CVE-2023-32686: 0.43% estimated exploitation activity in the next 30 days; percentile 37.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
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 upload validators in order to prevent potentially dangerous files from being uploaded, see GHSA-fwcf-753v-fgcj and Content-Security-Policy definition to prevent cross-site-scripting attacks, see GHSA-2wcr-87wf-cf9j. The upload validation checks were not robust enough which left the possibility of an attacker to circumvent them and upload a potentially dangerous file. Exploting this flaw a combination of files could be uploaded so that they work together to circumvent the existing Content-Security-Policy and allow execution of arbitrary JavaScript in the browser. Patches - File upload validation code has been improved - Kiwi TCMS will now force Content-Type: text/plain when serving uploaded files Workarounds 1) Force the Content-Type header via a custom Django middleware, see ExtraHeadersMiddleware in…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-x7c2-7wvg-jpx7
- Revision 1 · created ·
Published from osv record GHSA-x7c2-7wvg-jpx7
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2023-32686 Advisory: kiwitcms vulnerable to stored XSS via unrestricted files upload IDs: CVE-2023-32686, GHSA-x7c2-7wvg-jpx7 Record: https://patchnext.com/advisories/cve-2023-32686 (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: Medium (CVSS 5.4) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: kiwitcms 12.3. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI kiwitcms: affected < 12.3; fixed in 12.3 ## 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-x7c2-7wvg-jpx7 (OSV record GHSA-x7c2-7wvg-jpx7 lists affected ranges: PyPI kiwitcms >=0 <12.3 (fixed)) - Verified: https://github.com/advisories/GHSA-x7c2-7wvg-jpx7 (GitHub-reviewed advisory GHSA-x7c2-7wvg-jpx7 lists affected ranges: PyPI kiwitcms >=0 <12.3) Commands are suggestions: review each one before running it.
Loading voting…