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

CVE-2026-4084

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-21
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

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 fyyd podcast shortcodes plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'fyyd-podcast', 'fyyd-episode', and 'fyyd' shortcodes in all versions up to, and including, 0.3.1. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes such as 'color', 'podcast_id', and 'podcast_slug'. These attributes are directly concatenated into inline JavaScript within single-quoted string arguments without any escaping or sanitization, allowing an attacker to break out of the JavaScript string context. 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 fyyd podcast shortcodes WordPress plugin up to version 0.3.1 suffers from stored XSS via multiple shortcodes ('fyyd-podcast', 'fyyd-episode', 'fyyd'). User-supplied attributes (color, podcast_id, podcast_slug) are directly concatenated into inline JavaScript within single-quoted strings without sanitization or escaping, allowing attackers to break out of the JS string context.

MitigationUpdate the plugin to a patched version if available; otherwise, implement proper input sanitization using WordPress sanitization functions and output escaping (esc_js()) for attributes before inserting them into JavaScript contexts.

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. Confirm plugin installation and version
    Check the plugin files in wp-content/plugins/ for a directory named 'fyyd-podcast-shortcodes' or similar. Open the main PHP file and look for the 'Version' header comment. Alternatively, go to WordPress Admin > Plugins and look for the fyyd plugin.
    Affected if The installed version is 0.3.1 or lower.
  2. Identify shortcode usage in content
    Search the wp_posts table in the WordPress database for posts containing the shortcodes [fyyd-podcast], [fyyd-episode], or [fyyd] in the post_content field. Use SQL: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%[fyyd%'
    Affected if Any of these shortcodes are present in published content.
  3. Inspect shortcode handler code for vulnerable pattern
    Open the plugin PHP file that handles the shortcode (typically the main plugin file). Look for the shortcode callback function. Search for patterns where attributes like 'color', 'podcast_id', or 'podcast_slug' are directly concatenated into JavaScript strings, especially within single quotes, without passing through sanitization functions.
    Affected if The code shows direct concatenation of shortcode attributes into inline JavaScript (e.g., echo '<script>...'.$_GET['color'].'...</script>') without esc_js() or similar escaping.
  4. Check for presence of vulnerable attributes in shortcode definitions
    In the shortcode handler code, examine how attributes are defined and used. Look specifically for lines that insert 'color', 'podcast_id', or 'podcast_slug' attributes into script tags or JS variable assignments.
    Affected if The shortcode accepts these user-controllable attributes and places them directly into JavaScript context.

You are affected if the fyyd podcast shortcodes plugin version 0.3.1 or lower is installed AND any of the vulnerable shortcodes ([fyyd-podcast], [fyyd-episode], [fyyd]) are in use with user-supplied attributes, AND the plugin code contains the direct concatenation pattern into JavaScript.

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

Update the plugin to a patched version if available; otherwise, implement proper input sanitization using WordPress sanitization functions and output escaping (esc_js()) for attributes before inserting them into JavaScript contexts.

Have this fixed 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 help mitigating

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-2026-4084 — 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-4084 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