CVE-2026-97354

PowerPress 11.13.12 - 11.17.9 - Authenticated (Contributor+) Server-Side Request Forgery

2026-10-05 00:00
Raj Ukani

Strategic Overview

Status
Patched in 11.17.11
Affected Version
11.13.12 – 11.17.9
CVSS
6.4Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2026-97354
View all PowerPress Podcasting plugin by Blubrry vulnerabilities

At a glance

CVE-2026-97354 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the PowerPress Podcasting plugin by Blubrry WordPress plugin, affecting versions 11.13.12 – 11.17.9. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 11.17.11; sites on affected versions should update now. Disclosed October 2026, reported by Raj Ukani.

Vulnerability Overview

The PowerPress plugin for WordPress is vulnerable to Server-Side Request Forgery in versions 11.13.12 through 11.17.9. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.

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 interaction from a victim user.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in PowerPress Podcasting plugin by Blubrry 11.13.12 – 11.17.9 takes an account at Contributor level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For PowerPress Podcasting plugin by Blubrry the fix is 11.17.11: builds 11.13.12 – 11.17.9 are affected, anything from 11.17.11 onward is not.

Remediation

Update to version 11.17.11, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: PowerPress Podcasting plugin by Blubrry 11.17.11 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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