dbcve.org
Podlove Podcast PublisherWordPress extension · Podlove

CVE-2023-25472

HIGH · 8.8 CVSS v3.1 Published 2023-05-23
Fix available
A fix is available. Upgrade to 3.8.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Podlove Podlove Podcast Publisher plugin <= 3.8.3 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Podlove Podcast Publisher WordPress plugin versions 3.8.3 and below allows attackers to trick authenticated users into performing unintended actions by forging malicious requests.

MitigationUpdate the Podlove Podcast Publisher plugin to a version newer than 3.8.3 which contains the CSRF fix; additionally, implement anti-CSRF tokens (nonces) on all state-changing operations and verify referrer headers.

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:< 3.8.4

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
    Navigate to WordPress Admin > Plugins > Installed Plugins and search for 'Podlove Podcast Publisher' or 'Podlove' in the plugin list
    Affected if The plugin is not found in the installed plugins list
  2. Identify the installed version number
    In the plugins list, find the Podlove Podcast Publisher entry and locate the version number displayed beneath the plugin name (e.g., 'Version 3.8.3')
    Affected if The displayed version is 3.8.3 or any version below 3.8.4 (e.g., 3.8.2, 3.8.1, 3.8.0, etc.)
  3. Verify the plugin is active
    In WordPress Admin > Plugins > Installed Plugins, confirm the Podlove Podcast Publisher shows 'Active' status rather than 'Inactive'
    Affected if The plugin is active and the version is 3.8.3 or below - only active installations with the vulnerable version are at risk
  4. Check plugin files for version constant (alternative method)
    If available via file manager or FTP, inspect the main plugin file (usually wp-content/plugins/podlove-podcasting-plugin-for-wordpress/podlove.php) and look for a version definition like 'Version: x.x.x' in the file header comment
    Affected if The version found in the plugin file header is below 3.8.4

A user is affected if the Podlove Podcast Publisher plugin is installed, active, and running version 3.8.3 or any version lower than 3.8.4.

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 3.8.4 or later
Fixed in 3.8.4
Interim mitigation

Update the Podlove Podcast Publisher plugin to a version newer than 3.8.3 which contains the CSRF fix; additionally, implement anti-CSRF tokens (nonces) on all state-changing operations and verify referrer headers.

Recommended fix High confidence

Podlove Podcast Publisher version 3.8.4 or higher

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'Podlove Podcast Publisher' in the plugin list
  5. 5. If an update is available, click 'Update Now' to upgrade to version 3.8.4 or higher
  6. 6. Alternatively, download version 3.8.4 or later from the WordPress Plugin Repository
  7. 7. Deactivate the current plugin, then delete it, then upload and activate the new version
  8. 8. Verify the plugin is running version 3.8.4 or higher under Plugins > Installed Plugins

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

Fix this in Podlove Podcast Publisher Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25472 — 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-2023-25472 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