VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

privatebin/privatebin: vulnerability history, versions and safety

privatebin/privatebin is a package in the Packagist ecosystem. Vulert records 8 vulnerabilities for it across 35 releases, from Jan 2020 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded H1 M5 L2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
5 in the last 12 months

Most recent disclosure 28 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all privatebin/privatebin vulnerabilities

Vulert verdict on privatebin/privatebin i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 28 Aug 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 8 vulnerabilities on record across 6 years, 5 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 8 over 6 years · 5 in the last year i
  • Latest disclosure 28 Aug 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for privatebin/privatebin, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.0.4 M1 L1 Yes Details →
2.0.3 M1 L1 Yes Details →
2.0.2 M2 L2 Yes Details →
2.0.1 M3 L2 Yes Details →
2.0.0 M3 L2 Yes Details →
1.7.9 M2 L2 Yes Details →
1.7.8 M3 L2 Yes Details →
1.7.7 M3 L2 Yes Details →
1.7.6 M1 L1 Yes Details →
1.7.5 M1 L1 Yes Details →
1.7.4 M1 L1 Yes Details →
1.7.3 M2 L1 Yes Details →
1.7.2 M2 L1 Yes Details →
1.7.1 M2 L1 Yes Details →
1.7.0 M2 L1 Yes Details →
1.6.2 M2 L1 Yes Details →
1.6.1 M2 L1 Yes Details →
1.6.0 M2 L1 Yes Details →
1.5.2 M2 L1 Yes Details →
1.5.1 M2 L1 Yes Details →
1.5.0 M2 L1 Yes Details →
1.4.0 M1 L1 Yes Details →
1.3.5 H1 M1 L1 Yes Details →
1.3.4 H1 M1 L1 Yes Details →
1.3.3 H1 M1 L1 Yes Details →
1.3.2 H1 M1 L1 Yes Details →
1.3.1 H1 M1 L1 Yes Details →
1.3 H1 M1 L1 Yes Details →
1.2.3 H1 M1 L1 Yes Details →
1.2.2 H1 M1 L1 Yes Details →
1.2.1 H1 M2 L1 Yes Details →
1.2 H1 M2 L1 Yes Details →
1.1.1 H1 M2 L1 Yes Details →
1.1 H1 M2 L1 Yes Details →
1.0 H1 M2 L1 Yes Details →

Newest 35 of 35 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2022 1
  • 2024 1
  • 2025 3
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 5 of the 8 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for privatebin/privatebin

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Persistent Cross-site Scripting vulnerability in PrivateBin 8.2 high 1.4.0 12 Apr 2022
Persistent XSS vulnerability in filename of attached file in PrivateBin 6.1 medium 1.2.2 14 Jan 2020
CVE-2025-62796: PrivateBin HTML Injection Vulnerability in Attachment Filenames 5.8 medium 2.0.2 28 Oct 2025
CVE-2025-64714: PrivateBin Local File Inclusion via Template Switching 5.8 medium 2.0.3 14 Nov 2025
CVE-2024-39899: PrivateBin URL Shortening Vulnerability 5.3 medium 1.7.4 10 Jul 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About privatebin/privatebin

Is privatebin/privatebin safe to use?

Vulert records 8 vulnerabilities for privatebin/privatebin in Packagist: 0 critical, 1 high, 5 medium and 2 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does privatebin/privatebin have?

8 vulnerabilities are recorded for privatebin/privatebin in the Packagist ecosystem: 0 critical, 1 high, 5 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new privatebin/privatebin vulnerabilities disclosed?

5 vulnerabilities were recorded for privatebin/privatebin in the last 12 months, and the oldest entry in this database dates to 14 Jan 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of privatebin/privatebin are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor privatebin/privatebin for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the privatebin/privatebin version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.