CVE-2020-5223

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with an admin-level account. High risk of data exposure.

Exploit odds

0.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-01-23 02:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:21 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.7% in the next 30 days (EPSS).
• Severity: 6.1 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-01-23 02:15 UTC

Last modified

2026-06-17 03:21 UTC

Exploit probability

0.7% · EPSS, next 30 days

Weakness

CWE-79 · Cross-site scripting

Record status

Modified

Affected

• Privatebin < 1.2.2
• Privatebin < 1.3.2

Attack profile CVSS 3.1 · 6.1

Attack vector

Local

Complexity

High

Privileges needed

High

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-5223.md and follow it. Check whether this project is affected by CVE-2020-5223. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge