PrivateBin allows shortening of URLs for other domains

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-39899: 0.63% estimated exploitation activity in the next 30 days; percentile 50.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

In v1.5 we introduced the YOURLS server-side proxy. The idea was to allow using the YOURLs URL shortener without running the YOURLs instance without authentication and/or exposing the authentication token to the public, allowing anyone to shorten any URL. With the proxy mechanism, anyone can shorten any URL pointing to the configured PrivateBin instance. The vulnerability allowed other URLs to be shortened, as long as they contain the PrivateBin instance, defeating the limit imposed by the proxy. Neither the confidentially of existing pastes on the server nor the configuration options including the YOURLs token are affected. Impact This issue only affects non-standard configurations of PrivateBin. Instances are affected if all of the following conditions are met: 1. The PrivateBin instance enables URL shortening. 2. A YOURLs URL shortener is used and it is configured not to be public and require authentication to shorten URLs. 3. A basepath, the YOURLs proxy mechanism and an…

Published by the source

10 Jul 2024, 14:25 UTC

Last modified by the source

1 Aug 2024, 05:04 UTC

Source last checked

26 Oct 2026, 14:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mqqj-fx8h-437j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-39899

Advisory: PrivateBin allows shortening of URLs for other domains
IDs: CVE-2024-39899, GHSA-mqqj-fx8h-437j
Record: https://patchnext.com/advisories/cve-2024-39899 (revision 1, source checked 26 Oct 2026, 14:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: privatebin/privatebin 1.7.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist privatebin/privatebin: affected >= 1.5.0, < 1.7.4; fixed in 1.7.4

## Suggested inspection (read-only)
- Packagist privatebin/privatebin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on privatebin/privatebin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mqqj-fx8h-437j (GitHub-reviewed advisory GHSA-mqqj-fx8h-437j lists affected ranges: Packagist privatebin/privatebin >=1.5.0 <1.7.4)

Commands are suggestions: review each one before running it.