Skip to main content
Vulnerability Database/CVE-2025-32945

CVE-2025-32945: Framasoft PeerTube Auth Bypass Vulnerability

CVE-2025-32945 is an authorization bypass flaw in Framasoft PeerTube that allows users to add playlists to other users' channels. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-32945 Overview

CVE-2025-32945 affects Framasoft PeerTube, an open-source federated video platform. The vulnerability allows an authenticated user to create playlists on another user's channel through the PeerTube REST API. The flawed code sets the playlist owner to the requesting user but assigns the associated channel ID without verifying ownership. This is categorized under [CWE-282: Improper Ownership Management]. The issue was addressed in PeerTube v7.1.1.

Critical Impact

Authenticated attackers can inject playlists into channels they do not own, enabling content integrity attacks against other users' channels on affected PeerTube instances.

Affected Products

  • Framasoft PeerTube versions prior to 7.1.1
  • PeerTube REST API endpoints handling playlist creation
  • Self-hosted PeerTube instances across the ActivityPub federation

Discovery Timeline

  • 2025-04-15 - CVE-2025-32945 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-32945

Vulnerability Analysis

The vulnerability exists in the PeerTube REST API playlist creation workflow. When a user submits a playlist creation request, the server records the requesting user as the playlist owner. The server then attaches the playlist to the videoChannelId supplied in the request body. The code path does not verify that the referenced channel belongs to the authenticated user.

An authenticated attacker with any valid account can therefore associate a new playlist with any arbitrary channel on the instance. This breaks the ownership boundary that normally isolates one user's channel content from another's. The result is a cross-user authorization failure limited to the playlist creation endpoint. See the JFrog Vulnerability Analysis on PeerTube for the detailed code path.

Root Cause

The root cause is a missing ownership check between the authenticated principal and the target videoChannelId parameter. The code trusts client-supplied channel identifiers without validating that the authenticated user owns the channel. This is a classic improper ownership management flaw under [CWE-282].

Attack Vector

Exploitation requires a valid, low-privilege PeerTube account and network access to the target instance. The attacker sends an authenticated HTTP request to the playlist creation endpoint, substituting the videoChannelId with the identifier of a channel owned by another user. The server accepts the request and creates the playlist under the victim's channel. No user interaction is required from the victim. Technical details are published in the JFrog Vulnerability Analysis on PeerTube.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2025-32945

Indicators of Compromise

  • Playlist creation records where the playlist owner userId does not match the owner of the referenced videoChannelId.
  • Unexpected playlists appearing on channels without a corresponding administrative action by the channel owner.
  • Spikes in POST /api/v1/video-playlists requests from newly registered or low-reputation accounts.

Detection Strategies

  • Audit the PeerTube database by joining the playlist table with the channel table and flagging rows where the playlist owner does not match the channel owner.
  • Review reverse proxy or application logs for authenticated playlist creation calls that reference videoChannelId values outside the caller's channel set.
  • Correlate account creation timestamps with playlist creation activity to identify abuse patterns from throwaway accounts.

Monitoring Recommendations

  • Forward PeerTube API logs to a centralized logging platform and alert on ownership mismatches between playlist creators and target channels.
  • Monitor instance moderation queues for user reports of unauthorized playlists on their channels.
  • Track the running PeerTube version across federated nodes and alert when instances remain below v7.1.1.

How to Mitigate CVE-2025-32945

Immediate Actions Required

  • Upgrade PeerTube to version 7.1.1 or later as published in the GitHub PeerTube Release v7.1.1.
  • Audit existing playlists for ownership mismatches and remove any created through unauthorized channel assignment.
  • Review account registration policies to limit abuse from automated or low-trust accounts.

Patch Information

Framasoft addressed the vulnerability in PeerTube v7.1.1. The release notes and source changes are available in the GitHub PeerTube Release v7.1.1. Administrators of federated instances should coordinate upgrades to maintain consistent authorization behavior across the network.

Workarounds

  • If immediate upgrade is not possible, disable new user registration to limit the pool of authenticated attackers.
  • Restrict access to the PeerTube REST API through reverse proxy rules that enforce rate limits on playlist creation endpoints.
  • Manually review newly created playlists and remove any that violate channel ownership until the patch is applied.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.