CVE-2026-54724

Kiwi TCMS has an Open Redirect via unvalidated next parameter in account confirmation endpoint

An open redirect vulnerability in the account confirmation endpoint allows an unauthenticated attacker to craft a URL hosted on a legitimate Kiwi TCMS instance that redirects victims to an arbitrary external domain. The attack surface is particularly relevant for phishing campaigns targeting Kiwi TCMS users, as the malicious link originates from a trusted organizational hostname.

This is an open redirect vulnerability (CWE-601). Any unauthenticated attacker can exploit it against any user of a Kiwi TCMS deployment.

The primary risk is phishing. Because Kiwi TCMS is typically deployed as an internal tool for engineering and QA teams, a redirect from the organization's own hostname carries high implicit trust. An attacker can use this endpoint to:

• Redirect victims to a credential-harvesting page styled to match the Kiwi TCMS or corporate SSO login.
• Bypass email security filters and link-reputation checks that allowlist the organization's domain.
• Distribute malware via a convincing "confirm your account" lure.

Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites. Typical impact: phishing and credential harvesting via a trusted domain.

CVE-2026-54724 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no 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. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-54724? CVE-2026-54724 is a medium-severity open redirect vulnerability in kiwitcms (pip), affecting versions <= 112.4. No fixed version is listed yet. Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites.
2. How severe is CVE-2026-54724? CVE-2026-54724 has a CVSS score of 6.1 (Medium). 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-2026-54724? kiwitcms (pip) versions <= 112.4 is affected.
4. Is there a fix for CVE-2026-54724? No fixed version is listed for CVE-2026-54724 yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is CVE-2026-54724 exploitable, and should I be worried? Whether CVE-2026-54724 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-2026-54724 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-2026-54724? No fixed version is listed yet. In the interim: Validate redirect destinations against an allowlist of permitted URLs or paths. Reject destinations that include an unexpected authority component.

Other vulnerabilities in kiwitcms