kiwi TCMS has possibility for user to update email address to unverified oneGHSA-7x6q-3v3m-cwjg
NONEGHSA-7x6q-3v3m-cwjg is a none-severity (CVSS 0) CWE-283 vulnerability in kiwitcms. A fix is available for kiwitcms — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-7x6q-3v3m-cwjg.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
kiwitcmsReal-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
In previous versions of Kiwi TCMS users were able to update their email addresses via the "My profile" admin page. This page allowed them to change the email address registered with their account without the ownership verification performed during account registration.
Patches
With Kiwi TCMS v12.2 or later it is not possible to edit the email field associated with a user account!
Workarounds
No workaround exists.
References
Disclosed by @novemberdad.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | kiwitcms | all versions | 12.2pip install --upgrade 'kiwitcms==12.2' |
Affected Products
kiwi tcmskiwitcmsDetection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update kiwitcms to 12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7x6q-3v3m-cwjg is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-7x6q-3v3m-cwjg in your dependencies?
Find it across PyPI, including transitive dependencies.