dbcve.org
Podlove Podcast PublisherWordPress extension · Podlove

CVE-2024-32812

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-24
Fix available
A fix is available. Upgrade to 4.0.12 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Server-Side Request Forgery (SSRF) vulnerability in Podlove Podlove Podcast Publisher.This issue affects Podlove Podcast Publisher: from n/a through 4.0.11.

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 · moderate confidence

Server-Side Request Forgery (SSRF) vulnerability in Podlove Podcast Publisher plugin allows attackers to make the server perform unintended requests, potentially accessing internal resources or bypassing network restrictions. The vulnerability affects all versions up to and including 4.0.11.

MitigationUpdate to the patched version of Podlove Podcast Publisher when available. In the meantime, restrict outgoing network connections from the web server and implement strict allowlist validation for any URLs the application processes.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Podlove Podcast PublisherWordPress extension
Affected:< 4.0.12

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Verify Podlove Podcast Publisher is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Podlove Podcast Publisher' in the list
    Affected if Plugin is installed and active on the site
  2. Check installed plugin version
    In the Plugins list, click on the plugin name or view the plugin details to see the version number displayed (e.g., 'Version 4.0.11' or lower)
    Affected if Version shown is below 4.0.12 (for example, 4.0.11, 4.0.10, etc.)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the plugin status shows 'Active' under the Podlove Podcast Publisher entry
    Affected if Plugin is active and the vulnerable URL-handling functionality is accessible to attackers
  4. Inspect plugin files for SSRF-prone features
    Check plugin directory wp-content/plugins/podlove-podcasting-plugin/ for PHP files that handle external URL requests (look for functions using wp_remote_get, file_get_contents with URLs, or cURL calls to user-controlled destinations)
    Affected if The plugin processes external URLs through its publishing or feed import features without strict allowlist validation

You are affected if Podlove Podcast Publisher is installed, active, and running version 4.0.11 or earlier.

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
Upgrade available Upgrade to 4.0.12 or later
Fixed in 4.0.12
Interim mitigation

Update to the patched version of Podlove Podcast Publisher when available. In the meantime, restrict outgoing network connections from the web server and implement strict allowlist validation for any URLs the application processes.

Recommended fix High confidence

4.0.12

  1. Log in to the WordPress admin dashboard where the Podlove Podcast Publisher plugin is installed
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Podlove Podcast Publisher plugin
  4. Check the current version to confirm it is below 4.0.12
  5. Click 'Update Now' to update the plugin to version 4.0.12
  6. Verify the update completed successfully by checking the plugin version after update

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

Fix this in Podlove Podcast Publisher Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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-2024-32812 — 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-2024-32812 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