Podlove Podcast Publisher < 2.3.16 - Cross-Site Request Forgery to Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.3.16
- Affected Plugin
- Podlove Podcast Publisher
- Affected Version
< 2.3.16- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2016-10941
At a glance
CVE-2016-10941 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Podlove Podcast Publisher WordPress plugin, affecting versions < 2.3.16. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.3.16; sites on affected versions should update now. Disclosed September 2016.
Vulnerability Overview
The podlove-podcasting-plugin-for-wordpress plugin before 2.3.16 for WordPress has XSS exploitable via CSRF.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Podlove Podcast Publisher < 2.3.16 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 Podlove Podcast Publisher the fix is 2.3.16: builds < 2.3.16 are affected, anything from 2.3.16 onward is not.
Remediation
Update to version 2.3.16, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Podlove Podcast Publisher: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Podlove Podcast Publisher 2.3.16 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Podlove Podcast Publisher
- 9.9CVE-2024-32139: Podlove Podcast Publisher <= 4.0.12 SQL Injection
CVE-2024-32139 - 9.8CVE-2026-13001: Podlove Podcast Publisher Arbitrary File Upload
CVE-2026-13001 - 9.8CVE-2025-10147: Podlove Podcast Publisher Arbitrary File Upload
CVE-2025-10147 - 9.8CVE-2021-24666: Podlove Podcast Publisher <= 3.5.5 SQL Injection
CVE-2021-24666 - 8.8CVE-2026-16099: Podlove Podcast Publisher PHP Object Injection
CVE-2026-16099 - 8.8CVE-2016-10942: Podlove Podcast Publisher < 2.3.16 SQL Injection
CVE-2016-10942 - 8.0CVE-2017-12949: Podlove Podcast Publisher <= 2.5.3 SQL Injection
CVE-2017-12949 - 7.2CVE-2026-66615: Podlove Podcast Publisher <= 4.5.4 Stored XSS
CVE-2026-66615
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C