← Back to results
Vulnerability record · public intelligence
CVE-2026-54724
MEDIUM

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

Published Sep 15, 2026 · Updated Nov 3, 2026

Severity · CVSSMEDIUM · Not scored
Known exploitationNot listed
EPSS / likelihood0.35%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

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

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

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.

Potential impact

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.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗
  3. Source repository ↗

Record history

Published Sep 15, 2026 · Last refreshed Nov 3, 2026