criticalCVE-2026-13001

CVE-2026-13001 in Podlove Podcast Publisher

The Podlove Podcast Publisher plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'podlove_handle_cache_files' function in all versions up to, and including, 4.5.1. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

ProductPodlove Podcast Publisher
CVSS9.8
EPSSNot scored yet
UpdatedJuly 15, 2026

Quick answer

Podlove Podcast Publisher should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • Podlove Podcast Publisher up to and including 4.5.1

Fixed versions

  • 4.5.2 or later

How to fix it

CVE-2026-13001 affects Podlove Podcast Publisher. In simple terms, an attacker may run commands or unsafe code if they can reach the vulnerable feature. Fix it by updating to 4.5.2 or later. If this system is online or used by admins, treat the fix as urgent.

  1. Find every place where Podlove Podcast Publisher is installed or used.
  2. Check if the version matches: Podlove Podcast Publisher up to and including 4.5.1.
  3. Update or apply the vendor fix: 4.5.2 or later.
  4. If you cannot update today, allow only trusted users and trusted networks.
  5. Turn off the affected feature or plugin if the vendor says that is safe to do.
  6. Check logs for crashes, strange requests, new admin actions, or unexpected access.
  7. Change secrets or passwords if you think data or admin access may have been exposed.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm the installed version or mitigation matches: 4.5.2 or later.
  • Confirm the affected feature is no longer exposed to untrusted users.
  • Run the affected workflow again and make sure it still works.
  • Review logs again after the fix for repeated suspicious activity.
  • Run a new Fixnx scan if this software is part of a public website.
  • Save the advisory link and proof of the fix in your change record.

Related categories

Trusted references

FAQ

What is affected by CVE-2026-13001?

Podlove Podcast Publisher versions listed as affected should be reviewed: Podlove Podcast Publisher up to and including 4.5.1.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.