Cross-Site Request Forgery (CSRF) in org.togglz:togglz-console (CVE-2020-28191)
Summary
Vulnerability in org.togglz:togglz-console (CVE-2020-28191). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.9.4 or later.
Original description
The description as published by the source.
The console in Togglz before 2.9.4 allows CSRF.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2020-28191 was discovered in org.togglz:togglz-console.
In plain terms, it is a CSRF flaw that lets attackers act as the victim.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "org.togglz:togglz-console CVE-2020-28191".
CVE-2020-28191 (org.togglz:togglz-console). Severity: Info. Category: CWE-352.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2020-28191) in org.togglz:togglz-console. In plain words, it is a CSRF flaw that lets attackers act as the victim.
Target versions of org.togglz:togglz-console (see vendor advisory). If running in production, identify exposure immediately.
Severity: Info. Low severity or not yet rated.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-352)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.togglz:togglz-console' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
org.togglz:togglz-consoleを grep し、稼働しているサービス・バージョンを把握する。 -
6Apply patch patch
Upgrade org.togglz:togglz-console to 2.9.4ステージング環境で 2.9.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web mend.io