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

CVE-2026-1382

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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
The fresh Podcaster plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'freshpodcaster' shortcode in all versions up to, and including, 1.0.7 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

The fresh Podcaster WordPress plugin is vulnerable to stored XSS via the 'freshpodcaster' shortcode. The plugin fails to properly sanitize and escape user-supplied attributes in the shortcode, allowing authenticated attackers with contributor-level access or higher to inject malicious JavaScript that executes when users view affected pages.

MitigationUpdate the fresh Podcaster plugin to version 1.0.8 or later which contains proper input sanitization and output escaping. Until patched, restrict contributor-level user permissions and audit existing content using the freshpodcaster shortcode.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Check fresh Podcaster plugin version
    In WordPress admin, go to Plugins > Installed Plugins > look for 'fresh Podcaster' or 'Podcaster' and note the version number displayed. Compare it to the affected version range (versions prior to 1.0.8).
    Affected if The installed version is earlier than 1.0.8
  2. Identify shortcode usage in content
    Search WordPress database or content for the '[freshpodcaster]' shortcode by reviewing posts, pages, and widgets. Use WP-CLI: wp db query "SELECT * FROM wp_posts WHERE post_content LIKE '%[freshpodcaster%'" or manually inspect recent posts/pages.
    Affected if The freshpodcaster shortcode is present in any published content
  3. Verify shortcode attributes are unsanitized
    Examine the plugin source code in wp-content/plugins/fresh-podcaster/ to see if the shortcode handler function sanitizes/escapes attributes. Look for functions like esc_attr(), sanitize_text_field(), or similar in the shortcode callback.
    Affected if The shortcode handler does not sanitize/escape the attributes before output
  4. Audit contributor-level user accounts
    In WordPress admin, go to Users > All Users and check for accounts with the 'Contributor' role. Count how many exist. Alternatively: wp user list --role=contributor
    Affected if Any contributor-level or higher users exist who could inject malicious shortcode attributes

A user is affected if the fresh Podcaster plugin version is below 1.0.8 AND the freshpodcaster shortcode is in use, allowing any contributor-level user to inject unsanitized attributes.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the fresh Podcaster plugin to version 1.0.8 or later which contains proper input sanitization and output escaping. Until patched, restrict contributor-level user permissions and audit existing content using the freshpodcaster shortcode.

Recommended fix Moderate confidence

fresh Podcaster version 1.0.8 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'fresh Podcaster' plugin
  4. Check if current version is 1.0.7 or below
  5. If vulnerable, click 'Update Now' to upgrade to the latest version
  6. Verify the update completed successfully
  7. Test that the freshpodcaster shortcode functions correctly after update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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