Podcast Player <= 8.3.0 - Unauthenticated Server-Side Request Forgery
Strategic Overview
- Status
- Patched in 8.3.1
- Affected Plugin
- Podcast Player – Your Podcasting Companion
- Affected Version
<= 8.3.0- CVSS
- 7.2High
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2026-14860
At a glance
CVE-2026-14860 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Podcast Player WordPress plugin, affecting versions <= 8.3.0. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 8.3.1; sites on affected versions should update now. Disclosed August 2026, reported by ApogeeBytes.
Vulnerability Overview
The Podcast Player plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 8.3.0. This is due to missing validation that rejected raw URLs supplied as feed keys in public (unauthenticated) requests, allowing any valid URL to be passed where only a registered feed key was expected. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application by supplying a raw URL as a feed identifier in public requests.
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, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in Podcast Player <= 8.3.0 takes no account at all. 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 Podcast Player the fix is 8.3.1: builds <= 8.3.0 are affected, anything from 8.3.1 onward is not.
Remediation
Update to version 8.3.1, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Podcast Player 8.3.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C