Kiwi TCMS's /init-db/ page renders and responds to requests after first use

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U · score source

EPSS

• CVE-2026-49292: 0.44% estimated exploitation activity in the next 30 days; percentile 38.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Kiwi TCMS provides the /init-db/ page as part of its setup mechanism for administrators who prefer a browser instead of the command line. In previous versions of Kiwi TCMS this page still renders and responds to requests even after first use. Impact The /init-db/ page does not require any user authentication because it is the first setup operation that needs to be executed in order for Kiwi TCMS to function. Database initialization happens before there are any user accounts available! While that looks serious at first the /init-db/ page is merely a proxy behind the /Kiwi/manage.py migrate command, which itself is designed to be reentrant. In the case of repeated access to the /init-db/ page after first use the output is: as shown on the screenshots below: <img width="1911" height="992" alt="2222" src="https://github.com/user-attachments/assets/9f661c71-b305-4380-aadf-0732321b3666" / <img width="1913" height="1020" alt="3333"…

Published by the source

2 Jul 2026, 20:55 UTC

Last modified by the source

13 Jul 2026, 16:42 UTC

Source last checked

26 Oct 2026, 13:46 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-v8rp-6xcv-fwgh

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-v8rp-6xcv-fwgh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-49292

Advisory: Kiwi TCMS's /init-db/ page renders and responds to requests after first use
IDs: CVE-2026-49292, GHSA-v8rp-6xcv-fwgh
Record: https://patchnext.com/advisories/cve-2026-49292 (revision 3, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI kiwitcms: affected <= 12.4

## Suggested inspection (read-only)
- `python -m pip show kiwitcms`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on kiwitcms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-v8rp-6xcv-fwgh (OSV record GHSA-v8rp-6xcv-fwgh lists affected ranges: PyPI kiwitcms >=0 <=12.4)
- Verified: https://github.com/advisories/GHSA-v8rp-6xcv-fwgh (GitHub-reviewed advisory GHSA-v8rp-6xcv-fwgh lists affected ranges: PyPI kiwitcms >=0 <=12.4)

Commands are suggestions: review each one before running it.