dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-13001

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Podlove Podcast Publisher WordPress plugin is vulnerable to arbitrary file uploads due to missing file type validation in the 'podlove_handle_cache_files' function. Unauthenticated attackers can upload arbitrary files to the server, potentially achieving remote code execution. The vulnerability affects all versions up to and including 4.5.1.

MitigationUpdate the Podlove Podcast Publisher plugin to version 4.5.2 or later to remediate the arbitrary file upload vulnerability. Conduct a forensic review to detect and remove any malicious files already uploaded to the server.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Podlove Podcast Publisher plugin
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'podlove-podcast-publisher' or 'podlove-publisher'. Inspect the main plugin file (usually podlove.php) to find the version header comment.
    Affected if The plugin folder exists and the version header shows 4.5.1 or lower.
  2. Verify the installed version
    Open the main plugin PHP file and look for the 'Version:' comment in the file header, or check the WordPress admin plugins page listing.
    Affected if The reported version is 4.5.1 or any version below 4.5.2.
  3. Confirm the plugin is active
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Verify that Podlove Podcast Publisher shows as 'Active'.
    Affected if The plugin is active and the version is 4.5.1 or below.
  4. Inspect the cache directory for suspicious files
    Navigate to wp-content/plugins/podlove-podcast-publisher/lib/cache/ or wp-content/uploads/podlove-cache/ (the exact path depends on plugin configuration). Look for files with unusual extensions such as .php, .phtml, .exe, .sh, or files with double extensions like .php.jpg.
    Affected if Unexpected script files or suspicious file types are found in cache directories.
  5. Review access logs for upload attempts
    Examine web server access logs (Apache error.log, Nginx access.log) for POST requests to paths containing 'podlove_handle_cache_files' or similar cache-handling endpoints.
    Affected if Log entries show unauthenticated POST requests to cache upload functions from unknown IP addresses.

The environment is affected if Podlove Podcast Publisher version 4.5.1 or lower is installed and active, or if suspicious script files exist in plugin cache directories.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Podlove Podcast Publisher plugin to version 4.5.2 or later to remediate the arbitrary file upload vulnerability. Conduct a forensic review to detect and remove any malicious files already uploaded to the server.

Recommended fix Moderate confidence

Latest available version of Podlove Podcast Publisher (verify > 4.5.1)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Podlove Podcast Publisher plugin
  4. Check if an update is available and install the latest version
  5. Alternatively, download the latest version from the official WordPress plugin repository and upload it manually
  6. Verify the installed version is newer than 4.5.1 after updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA3.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13001 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data