CVE-2023-30613

Unrestricted file upload in kiwi TCMS

Workarounds

Upgrade to version 12.2 or later.

References

Originally reported by Ahmed Rabeaa Mosaa.

Kiwi TCMS allows users to upload attachments to test plans, test cases, etc. In earlier versions there is no control over what kinds of files can be uploaded. Thus a malicious actor may upload an .exe file or a file containing embedded JavaScript and trick others into clicking on these files causing vulnerable browsers to execute malicious code on another computer or attempting XSS attacks.

Stored XSS attacks via file uploads have been fixed in earlier versions of Kiwi TCMS, see GHSA-2wcr-87wf-cf9j. This advisory deals with prohibiting users to upload potentially compromised files in the first place.

The application accepts file uploads without adequately restricting the file type or content. Typical impact: remote code execution if the uploaded file can be served and executed on the server.

CVE-2023-30613 has a CVSS score of 7.7 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (12.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Kiwi TCMS v12.2 comes with functionality that allows administrators to configure additional upload validator functions which give them more control over what file types are accepted for upload. By default .exe are denied. Other files containing the <script> tag, regardless of their type are also denied b/c they are a path to XSS attacks.

1. What is CVE-2023-30613? CVE-2023-30613 is a high-severity unrestricted upload of dangerous file types vulnerability in kiwitcms (pip), affecting versions < 12.2. It is fixed in 12.2. The application accepts file uploads without adequately restricting the file type or content.
2. How severe is CVE-2023-30613? CVE-2023-30613 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of kiwitcms are affected by CVE-2023-30613? kiwitcms (pip) versions < 12.2 is affected.
4. Is there a fix for CVE-2023-30613? Yes. CVE-2023-30613 is fixed in 12.2. Upgrade to this version or later.
5. Is CVE-2023-30613 exploitable, and should I be worried? Whether CVE-2023-30613 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-30613 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-30613? Upgrade kiwitcms to 12.2 or later.

Other vulnerabilities in kiwitcms