← WordPress Vulnerabilities
WordPress security by component

Feeds for YouTube

Feeds for YouTube displays YouTube video feeds and channels on WordPress websites.

Feeds for YouTube (feeds-for-youtube) is a WordPress plugin with 4 published CVE records in this archive. The latest tracked vulnerability was published Jan 17, 2026; the highest published CVSS base score is 6.4.

Plugin slug: feeds-for-youtube

CVE-2025-12002: Feeds for YouTube Pro: Filesystem traversal

Feeds for YouTube Pro is affected by filesystem traversal. The vulnerable path is reachable without authentication. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.

PublishedJan 17, 2026
Safe version guidanceSee mitigation notes
Published vulnerabilities for feeds-for-youtube
Safe version
Jan 17, 2026 CVE-2025-12002
Feeds for YouTube Pro: Filesystem traversal
Feeds for YouTube Pro is affected by filesystem traversal. The vulnerable path is reachable without authentication. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.
See mitigation notes
CVE5.9
Dec 16, 2025 CVE-2025-64635
Feeds for YouTube: A security weakness
Feeds for YouTube is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.3
Jul 11, 2024 CVE-2024-6256
Feeds for YouTube (YouTube video, channel, and gallery plugin): Cross-site scripting
Feeds for YouTube (YouTube video, channel, and gallery plugin) is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
Sep 14, 2023 CVE-2023-4841
Feeds for YouTube: Cross-site scripting
Feeds for YouTube is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4