CVE-2025-15636
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in emarket-design YouTube Showcase youtube-showcase allows Stored XSS.This issue affects YouTube Showcase: from n/a through <= 3.5.1.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in emarket-design YouTube Showcase plugin allows authenticated attackers to inject malicious JavaScript through unsanitized input fields (likely YouTube URL or title parameters). The malicious script is stored in the database and executes when other users view the YouTube showcase pages.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm YouTube Showcase plugin is installedNavigate to WordPress admin > Plugins, or inspect wp-content/plugins directory for 'youtube-showcase' or 'emarket-design' folderAffected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionCheck the plugin main PHP file header (usually in the root plugin folder) for 'Version:' comment, or view in WordPress plugin admin pageAffected if Version cannot be determined or is unknown (assume affected if no patch available)
-
Verify YouTube showcase entries existCheck if any YouTube showcase posts/pages have been created in WordPress - look in the admin for entries under the YouTube Showcase post type, or query wp_posts table where post_type contains 'youtube' or 'showcase'Affected if Any YouTube showcase entries exist in the database
-
Inspect database for unsanitized input in YouTube URL or title fieldsQuery the database (wp_postmeta or wp_posts) for the YouTube showcase entries. Examine meta fields or content fields storing YouTube URLs and titles for unescaped HTML/script tags - look for patterns like <script>, javascript:, or event handlers in title/URL fieldsAffected if Raw HTML or JavaScript code is stored in YouTube URL or title fields without encoding
-
Check for stored XSS executionReview page source when viewing a YouTube showcase page in a browser. Look for unescaped user-supplied YouTube URLs or titles appearing in HTML output, particularly in href, src, or text content areasAffected if User-supplied YouTube URL or title parameters render as raw HTML instead of being HTML-encoded
If the YouTube Showcase plugin is installed and any showcase entries exist with unsanitized YouTube URL or title data in the database, the environment is affected by this stored XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of YouTube Showcase when available; until then, implement proper output encoding/sanitization on all user-supplied input fields and apply Content Security Policy headers to mitigate script execution.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15636 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-15636 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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