Veille CVE

Recherche « blubrry PowerPress Podcasting plugin by Blubrry »

5 CVE

Critique 0 Élevée 1 Moyenne 4 Faible 0 Non évaluée 0 Exploitées (KEV) Tri : plus récentes « blubrry PowerPress Podcasting plugin by Blubrry » ✕
  1. CVE-2026-97354 4.1 Moyenne

    Unknown PowerPress Podcasting plugin by Blubrry

    The PowerPress Podcasting plugin by Blubrry WordPress plugin before 11.17.11 does not validate the destination of redirects when fetching a user-supplied media URL, allowing users with the contributor role and above to perform Server-Side Request Forgery attacks against internal services.

  2. CVE-2026-97319 6.8 Moyenne

    Unknown PowerPress Podcasting plugin by Blubrry

    The PowerPress Podcasting plugin by Blubrry WordPress plugin before 11.17.2 does not sanitize and escape a block attribute before outputting it in a page, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.

  3. CVE-2026-16294 7.1 Élevée

    Unknown PowerPress Podcasting plugin by Blubrry

    The PowerPress Podcasting plugin by Blubrry WordPress plugin before 11.17.1 does not validate one of its Podcast Episode URL settings before performing a server-side request with it, allowing users with a role as low as Contributor to perform Server-Side Request Forgery attacks that can target internal services.

  4. CVE-2026-16293 6.8 Moyenne

    Unknown PowerPress Podcasting plugin by Blubrry

    The PowerPress Podcasting plugin by Blubrry WordPress plugin before 11.16.11 does not sanitise and escape some of its Podcast Episode settings, which could allow users with a role as low as Contributor to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed.

  5. CVE-2026-12098 6.4 Moyenne

    blubrry PowerPress Podcasting plugin by Blubrry

    The PowerPress Podcasting plugin by Blubrry plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'embed' Episode Meta Field in all versions up to, and including, 11.16.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The embed value is stored via update_post_meta() rather than through WordPress core's post content pipeline, meaning kses-on-save filtering is never applied — even for Author-role users who would otherwise lack unfiltered_html — making this path unprotected by WordPress's standard role-based XSS mitigations.