Cross-Site Scripting (XSS) in privatebin/privatebin (CVE-2020-5223)
Summary
Cross-site scripting in privatebin/privatebin (CVE-2020-5223). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.3.2 or later.
Original description
The description as published by the source.
In PrivateBin versions 1.2.0 before 1.2.2, and 1.3.0 before 1.3.2, a persistent XSS attack is possible. Under certain conditions, a user provided attachment file name can inject HTML leading to a persistent Cross-site scripting (XSS) vulnerability. The vulnerability has been fixed in PrivateBin v1.3.2 & v1.2.2. Admins are urged to upgrade to these versions to protect the affected users.
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 vulnerability tracked as CVE-2020-5223 has been found in privatebin/privatebin.
Risk of unauthorized operations or information disclosure.
What to do: upgrade privatebin/privatebin to 1.3.2 or later.
If unsure, ask your IT team or search "privatebin/privatebin CVE-2020-5223" on the vendor's site.
CVE-2020-5223 (privatebin/privatebin) — CWE-79
Attack vector: remote (network-reachable)
Patched: 1.3.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in privatebin/privatebin.
Check the vendor advisory for the affected versions of privatebin/privatebin.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.3.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'privatebin/privatebin' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'privatebin/privatebin' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
privatebin/privatebinを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade privatebin/privatebin to 1.3.2ステージング環境で 1.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- advisory privatebin.info
- patch github.com
- report github.com