CVE-2026-13001 json
Podlove Podcast Publisher <= 4.5.1 - Unauthenticated Arbitrary File Upload via podlove_image_cache_url Parameter
published 3mo ago modified 3mo ago also EUVD-2026-44402
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.8%
- EPSS 3.8% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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.
Patch / fix
Is CVE-2026-13001 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
3.76% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template Podlove Podcast Publisher <= 4.5.1 - Arbitrary File Upload nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- eteubert Podlove Podcast Publisher
Classification
- Weakness
-
- CWE-20 Improper Input Validation
- Technology feeds
References
- github.com /podlove/podlove-publisher/commit/5b32468601e903bae2bcacfaf36ff583d2bc9387
- wordfence.com /threat-intel/vulnerabilities/id/f81a3429-f378-4295-adbe-ad6f1df59701?source=cve
- plugins.trac.wordpress.org /browser/podlove-podcasting-plugin-for-wordpress/tags/4.4.2/lib/model/image.php#L439
- plugins.trac.wordpress.org /changeset/3597461/podlove-podcasting-plugin-for-wordpress
Sources
- CVE List CVE-2026-13001
- NVD CVE-2026-13001
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.