{"answers":{"affected":"2 open source packages ship an affected version, including privatebin/privatebin.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62796 exists.","fix":"Upgrade privatebin/privatebin to 2.0.2 or later.","what":"CVE-2025-62796 is a medium-severity cross-site scripting vulnerability in PrivateBin, published on 28 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-62796 and fix it if it is affected.\n\nWhat it is: CVE-2025-62796 is a medium-severity cross-site scripting vulnerability in PrivateBin, published on 28 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62796 exists.\n\nAffected packages and fixed versions:\n- privatebin/privatebin (Packagist): affected from 1.7.7; fixed in 2.0.2\n- privatebin/privatebin (Packagist): affected from 1.7.7; fixed in 2.0.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-2025-62796/ (Markdown: https://insights.sbomify.com/CVE-2025-62796/index.md)","id":"CVE-2025-62796","markdown":"https://insights.sbomify.com/CVE-2025-62796/index.md","name":"CVE-2025-62796","record":{"aliases":["GHSA-867c-p784-5q6g"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"PrivateBin pastebin","requires_auth":"none","summary":"Attackers can inject persistent HTML via attachment filenames in PrivateBin, enabling redirects and defacement if attachments are enabled.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-80","name":"Improper Neutralization of Script-Related HTML Tags in a Web Page"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"PrivateBin is an online pastebin where the server has zero knowledge of pasted data. Versions 1.7.7 through 2.0.1 allow persistent HTML injection via the unsanitized attachment filename (attachment_name) when attachments are enabled. An attacker can modify attachment_name before encryption so that, after decryption, arbitrary HTML is inserted unescaped into the page near the file size hint, enabling redirect (e.g., meta refresh) and site defacement and related phishing attacks. Script execution is normally blocked by the recommended Content Security Policy, limiting confidentiality impact. The issue was introduced in 1.7.7 and fixed in 2.0.2. Update to 2.0.2 or later. Workarounds include enforcing the recommended CSP, deploying PrivateBin on a separate domain, or disabling attachments.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"PrivateBin persistent HTML injection in attachment filename enables redirect and defacement","id":"CVE-2025-62796","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"CSRF in FluxCP account endpoints allows account takeover / state-changing actions","id":"CVE-2025-62797"},"packages":[{"ecosystem":"Packagist","fixed":["2.0.2"],"introduced":["1.7.7"],"last_affected":[],"package":"privatebin/privatebin","purl":null,"source":"GHSA-867c-p784-5q6g"},{"ecosystem":"Packagist","fixed":["2.0.2"],"introduced":["1.7.7"],"last_affected":[],"package":"privatebin/privatebin","purl":"pkg:composer/privatebin/privatebin","source":"GHSA-867c-p784-5q6g"}],"prev":{"headline":"JumpServer Unauthorized LDAP Configuration Access via WebSocket","id":"CVE-2025-62795"},"products":["PrivateBin"],"published":"2025-10-28","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-29","vendors":["PrivateBin"]},"summary":"Attackers can inject persistent HTML via attachment filenames in PrivateBin, enabling redirects and defacement if attachments are enabled.","url":"https://insights.sbomify.com/CVE-2025-62796/"}