PrivateBin persistent HTML injection in attachment filename enables redirect and defacement
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| PrivateBin | PrivateBin | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Privatebin | Privatebin | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-867c-p784-5q6g | PrivateBin is missing HTML sanitization of attached filename in file size hint |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.295% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Privatebin
Privatebin privatebin |
|
| Vendors & Products |
Privatebin
Privatebin privatebin |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | PrivateBin persistent HTML injection in attachment filename enables redirect and defacement | |
| Weaknesses | CWE-79 CWE-80 |
|
| References |
| |
| Metrics |
cvssV3_1
|