CVE-2026-49292

In Kiwi TCMS prior to 16.1, the account confirmation endpoint accepted an unvalidated next parameter, allowing an unauthenticated attacker to create a URL on a trusted Kiwi TCMS hostname that redirects a victim to an arbitrary external domain. The trusted origin can support credential-harvesting pages, bypass email security filters and link-reputation checks, or deliver malware through a convincing account-confirmation lure. This issue is fixed in version 16.1.

Kiwi TCMS is an open source test management system. Prior to 16.1, TestCase.extra_link and TestPlan.extra_link accepted unsanitized user input and rendered stored values verbatim, creating an opportunity for cross-site scripting. Official Docker images and unmodified Kiwi TCMS middleware send a Content-Security-Policy header that blocks inline JavaScript, making exploitation difficult in default deployments, while customized deployments that weaken those security settings may remain vulnerable. Version 16.1 properly sanitizes both fields and resets existing database records that do not validate to null. This issue is fixed in version 16.1.

Kiwi TCMS, a test management system, had an issue with incorrect Nginx configuration that allowed potentially dangerous scripts to be executed from attachments. Versions prior to 12.5 improperly handled the `Content-Type: text/plain` header, posing a risk to users.

Kiwi TCMS, a test management system, had vulnerabilities in file upload validation, allowing potentially dangerous files to be uploaded and arbitrary JavaScript execution in the browser. Additionally, Nginx's `proxy_pass` directive could strip some headers, weakening the protections of Kiwi TCMS when served behind a reverse proxy.