Skip to main content
Menu
CVEs

CVE

Kiwi TCMS open redirect in account confirmation page

CVE-2026-77433EUVD-2026-127357

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

6.1MediumCNA
Exploited
No known exploitation
Fix
Fixed in 16.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 16.2.

Published
Last modified
Reference
Last checked
13/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Kiwi TCMS, an open source test management system, has an incomplete fix for an open redirect flaw in its account confirmation page. An attacker can remotely, without logging in, craft a confirmation link on a trusted Kiwi TCMS address that sends a user who clicks it to an external site, which can enable phishing. The problem affects versions from 16.1 until 16.2 and is fixed in 16.2.

Written by a model from the sources below. Verify against them.

Original description

Kiwi TCMS is an open source test management system. From 16.1 until 16.2, the account confirmation page’s incomplete validation of the next parameter accepts protocol-relative URLs because the version 16.1 fix for CVE-2026-54724 only requires the value to start with a slash. An unauthenticated attacker can craft a confirmation URL on a trusted Kiwi TCMS hostname that redirects a user to an external site, enabling phishing and related downstream confidentiality or integrity impacts when the user follows the link. This issue is fixed in version 16.2.

cve.now Index

13Pcve.now Index 13 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.1/10CVSS 6.1
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 16.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77433 (Kiwi TCMS : Incomplete fix for CVE-2026-54724: open redirect bypass via protocol-relative URL in account confirmation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77433 (entry last updated 2026-11-17):
Affected:
- kiwitcms kiwitcms: from 16.1, fixed in 16.2
Fixed versions: 16.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77433 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77433 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/kiwitcms/kiwitcms/security/advisories/GHSA-gcwf-c25f-p9rv
- https://github.com/kiwitcms/kiwitcms/pull/4458
- https://github.com/kiwitcms/kiwitcms/commit/65d8f7c2743d7f06a4fca77c060b9d561f02f948
- https://github.com/kiwitcms/kiwitcms/releases/tag/v16.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77433
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77433"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • kiwitcms kiwitcms

    From 16.1 · fixed in 16.2

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Repository
  2. Repository
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-77433

Is CVE-2026-77433 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-77433?

kiwitcms: from 16.1 before 16.2.Source: cve.now feed data

How do I fix CVE-2026-77433?

Upgrade to a fixed version: 16.2.Source: cve.now feed data

More CVEs