Podlove Podcast Publisher <= 4.1.13 - Cross-Site Request Forgery to Remote Code Execution
Strategic Overview
- Status
- Patched in 4.1.14
- Affected Plugin
- Podlove Podcast Publisher
- Affected Version
<= 4.1.13- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-43984
At a glance
CVE-2024-43984 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Podlove Podcast Publisher WordPress plugin, affecting versions <= 4.1.13. 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 4.1.14; sites on affected versions should update now. Disclosed August 2024, reported by Muhammad Daffa.
Vulnerability Overview
The Podlove Podcast Publisher plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.1.13. This is due to missing or incorrect nonce validation on the 'get', 'update', 'create', and 'delete' functions. This makes it possible for unauthenticated attackers to modify templates and achieve remote code execution via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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)
Podlove Podcast Publisher <= 4.1.13 carries this weakness at get, and reaching it 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 4.1.14: builds <= 4.1.13 are affected, anything from 4.1.14 onward is not.
Remediation
Update to version 4.1.14, 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 4.1.14 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 8.8CVE-2016-10941: Podlove Podcast Publisher CSRF to Cross-Site Scripting
CVE-2016-10941 - 4.3CVE-2026-13729: Podlove Podcast Publisher < 4.5.3 CSRF
CVE-2026-13729 - 4.3CVE-2025-1383: Podlove Podcast Publisher <= 4.2.2 CSRF
CVE-2025-1383 - 4.3CVE-2023-25472: Podlove Podcast Publisher <= 3.8.3 CSRF
CVE-2023-25472
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