CVE-2026-49292

CVE-2026-49292 is a low-severity missing authorization vulnerability in kiwitcms (pip), affecting versions <= 12.4. No fixed version is listed yet.

Summary

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

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:

Running migrations:
  No migrations to apply.

as shown on the screenshots below:

  • There is no data loss because migrations result in a no-op if they are already applied!
  • No application state is altered because all state changes have already been applied!
  • No confidential information revealed because database migrations only report status on migrations which are clearly visible in source code!

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

Affected versions

kiwitcms (<= 12.4)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

The /init-db/ page has been modified to short-circuit itself if migrations have already been applied, resulting in a no-op on the webUI layer as well.

Frequently Asked Questions

  1. What is CVE-2026-49292? CVE-2026-49292 is a low-severity missing authorization vulnerability in kiwitcms (pip), affecting versions <= 12.4. No fixed version is listed yet. The application does not perform an authorization check before performing a sensitive operation.
  2. Which versions of kiwitcms are affected by CVE-2026-49292? kiwitcms (pip) versions <= 12.4 is affected.
  3. Is there a fix for CVE-2026-49292? No fixed version is listed for CVE-2026-49292 yet. Monitor the advisory for updates and apply mitigations in the interim.
  4. Is CVE-2026-49292 exploitable, and should I be worried? Whether CVE-2026-49292 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
  5. What actually determines whether CVE-2026-49292 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.
  6. How do I fix CVE-2026-49292? No fixed version is listed yet. In the interim: Keep the dependency up to date. Ensure authorization checks are enforced consistently on all sensitive operations.

Other vulnerabilities in kiwitcms

Stop the waste.
Protect your environment with Kodem.