Vulnerability 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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/PrivateBin/PrivateBin/commit/c4f8482b3072be7ae012cace1b3f5658
- https://github.com/PrivateBin/PrivateBin/pull/1550
- https://github.com/PrivateBin/PrivateBin/security/advisories/GHSA-867c-p784-5q6g
FAQ
What is CVE-2025-62796?
CVE-2025-62796 is a vulnerability with a CVSS score of 5.8 (MEDIUM). 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_na...
How severe is CVE-2025-62796?
CVE-2025-62796 has been rated MEDIUM with a CVSS base score of 5.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-62796?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.