{"answers":{"affected":"4 open source packages ship an affected version, including privatebin/privatebin. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-5223 in the wild and no public exploit code.","fix":"Upgrade privatebin/privatebin to a fixed version for your release line: 1.2.2 or 1.3.2.","what":"CVE-2020-5223 is a medium-severity cross-site scripting vulnerability in PrivateBin, published on 23 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-5223 and fix it if it is affected.\n\nWhat it is: CVE-2020-5223 is a medium-severity cross-site scripting vulnerability in PrivateBin, published on 23 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-5223 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- privatebin/privatebin (Packagist): affected all versions; fixed in 1.2.2\n- privatebin/privatebin (Packagist): affected all versions; fixed in 1.2.2\n- privatebin/privatebin (Packagist): affected from 1.3.0; fixed in 1.3.2\n- privatebin/privatebin (Packagist): affected from 1.3.0; fixed in 1.3.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-5223/ (Markdown: https://insights.sbomify.com/CVE-2020-5223/index.md)","id":"CVE-2020-5223","markdown":"https://insights.sbomify.com/CVE-2020-5223/index.md","name":"CVE-2020-5223","record":{"aliases":["GHSA-8j72-p2wm-6738"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PrivateBin","requires_auth":"high_privilege","summary":"Persistent XSS in PrivateBin allows attackers to inject HTML via attachment filenames, potentially executing scripts in victim browsers.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"privatebin","vendor":"privatebin"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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 \u0026 v1.2.2. Admins are urged to upgrade to these versions to protect the affected users.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Persistent XSS vulnerability in filename of attached file in PrivateBin","id":"CVE-2020-5223","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2020"},"n_packages":4,"n_references":4,"next":{"headline":"Session key exposure through session list in Django User Sessions","id":"CVE-2020-5224"},"packages":[{"ecosystem":"Packagist","fixed":["1.2.2"],"introduced":["0"],"last_affected":[],"package":"privatebin/privatebin","purl":null,"source":"GHSA-8j72-p2wm-6738"},{"ecosystem":"Packagist","fixed":["1.2.2"],"introduced":["0"],"last_affected":[],"package":"privatebin/privatebin","purl":"pkg:composer/privatebin/privatebin","source":"GHSA-8j72-p2wm-6738"},{"ecosystem":"Packagist","fixed":["1.3.2"],"introduced":["1.3.0"],"last_affected":[],"package":"privatebin/privatebin","purl":null,"source":"GHSA-8j72-p2wm-6738"},{"ecosystem":"Packagist","fixed":["1.3.2"],"introduced":["1.3.0"],"last_affected":[],"package":"privatebin/privatebin","purl":"pkg:composer/privatebin/privatebin","source":"GHSA-8j72-p2wm-6738"}],"prev":{"headline":"Hard-Coded Key Used For Remember-me Token in OpenCast","id":"CVE-2020-5222"},"products":["PrivateBin"],"published":"2020-01-23","related":[{"cvss_score":8.2,"headline":"Persistent Cross-site Scripting (XSS) vulnerability in PrivateBin","id":"CVE-2022-24833","kev_date_added":null,"published":"2022-04-11"},{"cvss_score":3.9,"headline":"PrivateBin vulnerable to malicious filename use for self-XSS / HTML injection locally for users","id":"CVE-2025-64711","kev_date_added":null,"published":"2025-11-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["PrivateBin"]},"summary":"Persistent XSS in PrivateBin allows attackers to inject HTML via attachment filenames, potentially executing scripts in victim browsers.","url":"https://insights.sbomify.com/CVE-2020-5223/"}