dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-32448

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Eric Teubert Podlove Podcast Publisher podlove-podcasting-plugin-for-wordpress allows Stored XSS.This issue affects Podlove Podcast Publisher: from n/a through <= 4.3.3.

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

A stored cross-site scripting (XSS) vulnerability exists in the Podlove Podcast Publisher WordPress plugin where user-supplied input is not properly sanitized before being rendered in web pages. This allows authenticated attackers to embed malicious JavaScript code that executes when other users access affected pages.

MitigationApply proper input sanitization using WordPress functions like sanitize_text_field() and implement output escaping with functions like esc_html() or esc_attr() when displaying data. Update to the latest patched version of the plugin when available.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Confirm Podlove Podcast Publisher is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Podlove Podcast Publisher' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active, making the XSS vector accessible.
  2. Identify the installed plugin version
    Click on the plugin name in the plugins list to view details, or check the plugin's main PHP file header for the 'Version' comment. Compare this to any official security advisories for this CVE.
    Affected if Running any version known to be affected by this CVE (check WordPress plugin repository or security mailing lists for specific vulnerable versions).
  3. Verify WordPress user authentication settings
    Navigate to Users > All Users in the WordPress admin. Review which user roles have access to plugin-specific input fields (podcast settings, episode metadata, chapter marks, etc.).
    Affected if Any authenticated user role (Contributor or higher) can access input fields where unsanitized data could be stored.
  4. Inspect plugin settings pages for input fields
    Go to the plugin settings pages (usually under Podcast > Episodes, Podcast > Settings, or similar). Look for text input fields, textarea fields, or custom fields where user content is saved to the database.
    Affected if Input fields exist that accept freeform text without visible sanitization indicators.
  5. Check for stored content in plugin database tables
    Use a database tool (phpMyAdmin or CLI) to examine wp_postmeta or custom plugin tables for any episode or podcast metadata containing HTML or script tags that were saved without escaping.
    Affected if Stored records contain unescaped HTML, script tags, or event handler attributes in fields that display on the frontend.

A defender is affected if the Podlove Podcast Publisher plugin is active, runs a version within the CVE-affected range, and any authenticated user can access plugin-specific input fields where unsanitized data can be saved and later rendered to other users.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply proper input sanitization using WordPress functions like sanitize_text_field() and implement output escaping with functions like esc_html() or esc_attr() when displaying data. Update to the latest patched version of the plugin when available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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