CVE
Kiwi TCMS unauthenticated user data disclosure in User.filter
- Exploited
- No known exploitation
- Fix
- Fixed in 8.6
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 8.6.
Summary
Kiwi TCMS before 8.6 contains a missing authorization vulnerability in the User.filter JSON-RPC method that allows unauthenticated attackers to retrieve user account information. Attackers can send a POST request to /json-rpc/ invoking User.filter with a query parameter to disclose sensitive user data without authentication. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 8.6.
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-2020-37290 (Kiwi TCMS < 8.6 Information Disclosure via User.filter JSON-RPC), 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-2020-37290 (entry last updated 2026-11-18):
Affected:
- Kiwi TCMS Kiwi TCMS: fixed in 8.6
Fixed versions: 8.6.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2020-37290 is not listed as of cve.now's last read.
This KEV status is for CVE-2020-37290 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://kiwitcms.org/blog/kiwi-tcms-team/2020/08/23/kiwi-tcms-86/
- https://github.com/kiwitcms/Kiwi/commit/f6b1898f827019e1daf4e98cd4ba1678da0025cf
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/kiwitcms-json-rpc.yaml
- https://www.vulncheck.com/advisories/kiwi-tcms-before-8.6-information-disclosure-via-user-filter-json-rpc
- https://www.vulncheck.com/advisories/kiwi-tcms-8.6-information-disclosure-via-user-filter-json-rpc
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-2020-37290
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-2020-37290"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Kiwi TCMS Kiwi TCMS
fixed in 8.6
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2020-37290 |
| Record | NVD · CVE-2020-37290 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Repository | GitHub · projectdiscovery/nuclei-templates · http/vulnerabilities/other/kiwitcms-json-rpc.yaml |
| Other links 4 | |
| Patch | kiwitcms.org · blog/kiwi-tcms-team/2020/08/23/kiwi-tcms-86 |
| Patch | GitHub · kiwitcms/Kiwi · Commit f6b1898f |
| Link | vulncheck.com · advisories/kiwi-tcms-before-8.6-information-disclosure-via-user-filter-json-rpc |
| Link | vulncheck.com · advisories/kiwi-tcms-8.6-information-disclosure-via-user-filter-json-rpc |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2020-37290
Is CVE-2020-37290 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-2020-37290?
Kiwi TCMS: before 8.6.Source: cve.now feed data
How do I fix CVE-2020-37290?
Upgrade to a fixed version: 8.6.Source: cve.now feed data