CVE-2023-32686
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKiwi TCMS is an open source test management system for both manual and automated testing. 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. The upload validation checks were not robust enough which left the possibility of an attacker to circumvent them and upload a potentially dangerous file. Exploiting 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. This issue has been patched in version 12.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceKiwi TCMS had inadequate file upload validation that could be bypassed, allowing dangerous files to be uploaded. By uploading a combination of files that work together, attackers could circumvent the Content-Security-Policy and achieve arbitrary JavaScript execution in users' browsers (stored XSS via CSP bypass).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 12.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Kiwi TCMS versionCheck the version number displayed in the Kiwi TCMS admin interface (typically at /admin/about/) or by inspecting the source code for the version string (often in setup.py, VERSION file, or the container image tags)Affected if The installed version is 12.2 or lower (<= 12.2)
-
Determine if file uploads are enabledNavigate to Kiwi TCMS settings or check if the upload functionality is accessible in the Test Runs or Attachments sections; inspect the Django settings file (settings.py) for UPLOAD_ENABLED or similar flagsAffected if File uploads are enabled and users can attach files to test cases or runs
-
Inspect file type validation logicReview the source code related to file uploads, typically in views or serializers that handle attachments; look for file type/extension validation functionsAffected if There is no or minimal validation (such as checking only Content-Type header without validating file content/magic bytes)
-
Check Content-Security-Policy header configurationInspect HTTP responses from Kiwi TCMS for the Content-Security-Policy header, or check the web server/Traefik configuration that serves Kiwi TCMSAffected if CSP allows inline scripts (unsafe-inline) or does not properly restrict script sources, allowing uploaded files to execute JavaScript
You are affected if Kiwi TCMS version is 12.2 or lower AND file uploads are enabled with inadequate validation, allowing CSP bypass for stored XSS.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Kiwi TCMS version 12.3 or later which contains the patch. If immediate upgrade is not possible, consider disabling file uploads or adding supplementary file validation at the web server level.
12.3
- Back up your current Kiwi TCMS installation and database before upgrading
- Upgrade Kiwi TCMS to version 12.3 or later
- Verify the upgrade was successful by logging into the application
- Test file upload functionality to ensure the patch is working correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32686 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-32686 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data