Is privatebin/privatebin affected by CVE-2025-64711?

Packagist privatebin/privatebin is affected in >=1.7.7 <2.0.3.

Is CVE-2025-64711 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.1%.

low

CVE-2025-64711

Q: Is CVE-2025-64711 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.1%.

Packagist · privatebin/privatebin

Summary

PrivateBin vulnerable to malicious filename use for self-XSS / HTML injection locally for users

Severity: low
EPSS: 0.1% (p1)
Also known as: GHSA-r9x7-7ggj-fx9f
Published: 2025-11-14

References

https://github.com/PrivateBin/PrivateBin/security/advisories/GHSA-r9x7-7ggj-fx9f
https://nvd.nist.gov/vuln/detail/CVE-2025-64711
https://github.com/PrivateBin/PrivateBin/commit/f9550e513381208b36595ee2404e968144bba78b

Related advisories

CVE-2025-64714 — medium · Packagist/privatebin/privatebin
CVE-2025-62796 — medium · Packagist/privatebin/privatebin
CVE-2024-39899 — medium · Packagist/privatebin/privatebin

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.