CVE-2026-16099 Deserialization in Podlove Podcast Publisher
Authenticated attackers can exploit PHP object injection to delete arbitrary files, potentially leading to remote code execution.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-16099?
CVE-2026-16099 is a high-severity unsafe deserialization vulnerability in eteubert Podlove Podcast Publisher, published on 16 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
The Podlove Podcast Publisher plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the create_link_item function in all versions up to, and including, 4.5.3. This makes it possible for authenticated attackers, with contributor-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). A viable POP chain exists within the plugin itself via Podlove\ImageCache\GenerationGuard, whose __destruct() method invokes wp_delete_file() with an attacker-controlled file path populated through unserialization.
Weakness: CWE-502
Which versions are affected by CVE-2026-16099?
How do I fix CVE-2026-16099?
No fix has been published for CVE-2026-16099 yet. Limit exposure of the affected software until one is available.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2026-16099 being exploited?
There is no known exploitation of CVE-2026-16099 in the wild and no public exploit code.
Sources
Also known as GHSA-q83h-6954-x259.