CVE-2020-28191 json
Togglz console missing cross-site request forgery (CSRF) protection
published 4y ago modified 4mo ago also GHSA-697v-pxg3-j262 , EUVD-2022-6261
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
The console in Togglz before 2.9.4 allows CSRF.
Patch / fix
- maven org.togglz:togglz-console 2.9.4
- togglz togglz 2.9.4
- github.com/togglz/togglz@ed66e3f commit
- github.com/togglz/togglz#495 pull request
Is CVE-2020-28191 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.togglz:togglz-console | <2.9.4 |
2.9.4 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/togglz/togglz/pull/495
web, patch, third-party-advisory
-
github.com
/togglz/togglz/commit/ed66e3f584de954297ebaf98ea4a235286784707
web, patch, third-party-advisory
-
github.com
/advisories/GHSA-697v-pxg3-j262
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-28191
advisory
-
github.com
/togglz/togglz
package
-
mend.io
/vulnerability-database/CVE-2020-28191
web
Sources
- CVE List CVE-2020-28191
- GitHub Advisory GHSA-697v-pxg3-j262
- NVD CVE-2020-28191
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.