CVE-2026-13001: Podlove Podcast Publisher arbitrary file upload in podlove_handle_cache_files

CVE-2026-13001 · Severity: critical · CVSS 9.8 · Published 2026-07-14

The Podlove Podcast Publisher plugin for WordPress, used for managing and publishing podcast feeds, contains a security flaw in its image caching system. An unauthenticated attacker can upload malicious files, such as PHP scripts, to the web server by disguising them as images. If successful, this allows the attacker to take complete control of the website, potentially leading to data theft, site defacement, or the installation of malware.

Technologies: Podlove Podcast Publisher. Vendors: Podlove.

Quick answers

Is CVE-2026-13001 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-13001 being exploited in the wild.
How severe is CVE-2026-13001?
Critical severity, with a CVSS score of 9.8, published 14 July 2026.
Which products and versions are affected?
Podlove Podcast Publisher <= 4.5.1.
Is there a fix for CVE-2026-13001?
A patch was published on 2026-06-27: Fix committed to GitHub repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-13001 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-13001?
Check whether you run Podlove Podcast Publisher at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The Podlove Podcast Publisher plugin for WordPress is vulnerable to arbitrary file uploads via the 'podlove_handle_cache_files' function in versions up to and including 4.5.1. The vulnerability stems from a logic flaw where the plugin derived the final cache file extension from the remote URL path while performing validation on a different filename derived from the full source URL. This allowed 'polyglot' files (e.g., payload.php?.heic) to pass image validation while being stored on the server with an executable .php extension. An unauthenticated attacker can exploit this to upload malicious scripts and achieve remote code execution. The issue has been addressed in subsequent versions by enforcing safe image extensions and validating the downloaded file type against the stored extension.

Affected products

  • eteubert Podlove Podcast Publisher <= 4.5.1

Timeline

  • 2026-06-27: patched: Fix committed to GitHub repository
  • 2026-07-14: disclosed: CVE published and advisory released by Wordfence

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.