CVE-2025-10147
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 · uneditedThe Podlove Podcast Publisher plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'move_as_original_file' function in all versions up to, and including, 4.2.6. 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 confidenceThe Podlove Podcast Publisher WordPress plugin lacks file type validation in its move_as_original_file function, allowing unauthenticated attackers to upload arbitrary files directly to the server. This enables potential remote code execution by uploading malicious PHP files or other executables.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Podlove Podcast Publisher plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Podlove Podcast Publisher' in the list. Check if it shows as 'Active'.Affected if Plugin is installed and active, exposing the vulnerable function.
-
Identify installed plugin versionClick on the plugin name in the Plugins list to view details, or open the main plugin file (podlove/podlove.php) and locate the 'Version:' header in the plugin comments at the top.Affected if Version number is below 4.2.7.
-
Compare version to affected rangeCompare the installed version number you found to the affected range. Versions prior to 4.2.7 lack proper file type validation in the move_as_original_file function.Affected if Installed version is less than 4.2.7.
-
Confirm upload functionality exposureThe vulnerability exists in the move_as_original_file function. If the plugin handles file uploads (podcast media files), this function processes them without validating file types. Check if the plugin settings allow file uploads or if the web server serves the wp-content/uploads/ directory.Affected if Plugin is active and handles file uploads without additional access controls blocking the vulnerable endpoint.
User is affected if Podlove Podcast Publisher plugin is active with a version lower than 4.2.7 and the upload functionality is accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the Podlove Podcast Publisher plugin to version 4.2.7 or later which includes proper file type validation. Until patched, consider disabling the plugin or deploying WAF rules to block malicious file uploads.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10147 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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