CVE-2023-33931

YouTube Playlist Player <= 4.6.4 - Cross-Site Request Forgery in ytpp_settings

2023-05-23 00:00
Skalucy

Strategic Overview

Status
Patched in 4.6.5
Affected Version
<= 4.6.4
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-33931
View all Playlist Player for YouTube vulnerabilities

At a glance

CVE-2023-33931 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Playlist Player for YouTube WordPress plugin, affecting versions <= 4.6.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.6.5; sites on affected versions should update now. Disclosed May 2023, reported by Skalucy.

Vulnerability Overview

The YouTube Playlist Player plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.6.4. This is due to missing or incorrect nonce validation on the ytpp_settings function. This makes it possible for unauthenticated attackers to modify plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Playlist Player for YouTube <= 4.6.4 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Playlist Player for YouTube the fix is 4.6.5: builds <= 4.6.4 are affected, anything from 4.6.5 onward is not.

Remediation

Update to version 4.6.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Playlist Player for YouTube: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Playlist Player for YouTube 4.6.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Other vulnerabilities in Playlist Player for YouTube

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C