CVE-2024-52393

Podlove Podcast Publisher <= 4.1.15 - Authenticated (Admin+) Remote Code Execution

2024-11-11 00:00
Hakiduck

Strategic Overview

Status
Patched in 4.1.17
Affected Plugin
Podlove Podcast Publisher
Affected Version
<= 4.1.15
CVSS
7.2High
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2024-52393
View all Podlove Podcast Publisher vulnerabilities

At a glance

CVE-2024-52393 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Podlove Podcast Publisher WordPress plugin, affecting versions <= 4.1.15. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 4.1.17; sites on affected versions should update now. Disclosed November 2024, reported by Hakiduck.

Vulnerability Overview

The Podlove Podcast Publisher plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.1.15. This makes it possible for authenticated attackers, with administrator-level access and above, to execute code on the server.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in Podlove Podcast Publisher <= 4.1.15 takes an account at Admin level or above. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Podlove Podcast Publisher the fix is 4.1.17: builds <= 4.1.15 are affected, anything from 4.1.17 onward is not.

Remediation

Update to version 4.1.17, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Podlove Podcast Publisher 4.1.17 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-52393https://www.wordfence.com/threat-intel/vulnerabilities/id/70b18fd0-41e5-4679-a7a5-3dd6eaa29136https://nvd.nist.gov/vuln/detail/CVE-2024-52393

Related records

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