How severe is GHSA-v8rp-6xcv-fwgh?

No CVSS score has been assigned to GHSA-v8rp-6xcv-fwgh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v8rp-6xcv-fwgh?

GHSA-v8rp-6xcv-fwgh affects the following packages: kiwitcms (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-v8rp-6xcv-fwgh?

No patched version of kiwitcms has shipped for GHSA-v8rp-6xcv-fwgh yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-v8rp-6xcv-fwgh in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kiwitcms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-v8rp-6xcv-fwgh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-v8rp-6xcv-fwgh?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v8rp-6xcv-fwgh can be triaged on real exposure rather than presence alone.

Is GHSA-v8rp-6xcv-fwgh actively exploited in the wild?

No public exploit code has been indexed for GHSA-v8rp-6xcv-fwgh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-v8rp-6xcv-fwgh?

GHSA-v8rp-6xcv-fwgh has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 18th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-v8rp-6xcv-fwgh?

GHSA-v8rp-6xcv-fwgh is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-v8rp-6xcv-fwgh published, and has it been updated?

GHSA-v8rp-6xcv-fwgh was published on July 2, 2026 and was last updated on July 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-v8rp-6xcv-fwgh — kiwitcms

GHSA-v8rp-6xcv-fwgh is a CWE-862 vulnerability in kiwitcms. No vendor fix is recorded yet; mitigation options are listed below.

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

Also known asCVE-2026-49292PYSEC-2026-2553

Published

Jul 2, 2026

Updated

Jul 13, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-v8rp-6xcv-fwgh.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs18th percentile — riskier than 18% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐍kiwitcms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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!

Remediation

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`kiwitcms`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kiwitcms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of kiwitcms has shipped for GHSA-v8rp-6xcv-fwgh yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v8rp-6xcv-fwgh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-v8rp-6xcv-fwgh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 migr

O3 Security · Impact-Aware SCA

Is GHSA-v8rp-6xcv-fwgh in your dependencies?

O3 Security finds GHSA-v8rp-6xcv-fwgh across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works