morpheus65535 Bazarr up to 1.5.7-beta.13 Plex OAuth Handlers bazarr/api/plex/oauth.py write_config state_param server-side request forgery

Summaryinfo

A vulnerability, which was classified as critical, has been found in morpheus65535 Bazarr up to 1.5.7-beta.13. Affected is the function write_config of the file bazarr/api/plex/oauth.py of the component Plex OAuth Handlers. This manipulation of the argument state_param causes server-side request forgery. This vulnerability is handled as CVE-2026-61826. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability has been found in morpheus65535 Bazarr up to 1.5.7-beta.13 and classified as critical. Affected by this vulnerability is the function write_config of the file bazarr/api/plex/oauth.py of the component Plex OAuth Handlers. The manipulation of the argument state_param with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Bazarr is a companion application to Sonarr and Radarr. Prior to 1.5.7-beta.14, the `api_ns_plex` namespace in `bazarr/api/plex/oauth.py` omits `@authenticate` on its Resource handlers, while normal APIs require an API key and no global authentication hook compensates. Anonymous callers can invoke `POST /api/plex/oauth/logout` to clear credentials and disable the integration, or `POST /api/plex/apikey` to persist an attacker-selected key, without a PIN, account or state precondition. `POST /api/plex/oauth/pin` and `GET /api/plex/oauth/pin/<pin_id>/check` additionally allow an attacker who completes a PIN with an attacker-controlled Plex account to bind that account's token to the instance. `PlexPinCheck` skips state validation when `state_param` is absent and merely logs a mismatch without stopping execution. `POST /api/plex/select-server`, `POST /api/plex/oauth/servers`, `POST /api/plex/webhook/create`, `POST /api/plex/webhook/delete` and `POST /api/plex/encrypt-apikey` expose further `write_config()` operations. Attacker-controlled server URLs feed later outbound requests carrying the configured API key in `X-Plex-Token`, enabling server-side request forgery and credential exposure in addition to persistent configuration tampering and integration denial of service. Version 1.5.7-beta.14 closes the anonymous API-mutation path by adding authentication; complete OAuth state validation is not established and remains a separate residual for curator review.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-61826 since 07/10/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.

Upgrading to version 1.5.7-beta.14 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• morpheus65535

Name

• Bazarr

Version

• 1.5.7-beta.0
• 1.5.7-beta.1
• 1.5.7-beta.2
• 1.5.7-beta.3
• 1.5.7-beta.4
• 1.5.7-beta.5
• 1.5.7-beta.6
• 1.5.7-beta.7
• 1.5.7-beta.8
• 1.5.7-beta.9
• 1.5.7-beta.10
• 1.5.7-beta.11
• 1.5.7-beta.12
• 1.5.7-beta.13

Website

• Product: https://github.com/morpheus65535/bazarr/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion