LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1825: Show YouTube video <= 1.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'id' Shortcode Attribute

The Show YouTube video plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'syv' shortcode in all versions up to, and including, 1.1 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.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1825 affects the WordPress “Show YouTube video” plugin through version 1.1. A logged-in user with Contributor-level access or higher can store script content in a shortcode attribute, causing it to run when others view the page. This is not listed as actively exploited in KEV.

Executive priority

Treat as a targeted website integrity and user-risk issue, not an emergency wormable flaw. Prioritize sites with many content contributors, public registration, or sensitive administrator sessions.

Technical view

The issue is stored cross-site scripting in the plugin’s 'syv' shortcode 'id' attribute, caused by insufficient sanitization and output escaping. CVSS 3.1 is 6.4, with low-privileged authenticated access required and changed scope. Public references point to plugin code locations in version 1.1.

Likely exposure

Exposure is limited to WordPress sites running Show YouTube video version 1.1 or earlier, especially where Contributor or higher accounts are available to untrusted users.

Exploitation context

An attacker needs authenticated WordPress access at Contributor level or above. Successful abuse could affect site visitors or administrators who view injected content. The provided sources do not show active exploitation.

Researcher notes

The source bundle states versions up to and including 1.1 are vulnerable, while the affected metadata appears inconsistent. Validate against Wordfence and plugin repository evidence before broad asset tagging. No patch version is identified in the provided sources.

Mitigation direction

  • Check vendor or WordPress plugin guidance for a fixed version or advisory.
  • If no fix is available, consider disabling the plugin until remediated.
  • Restrict Contributor and higher roles to trusted users only.
  • Review content workflows for shortcode use by lower-privileged authors.

Validation and detection

  • Inventory WordPress sites for the Show YouTube video plugin.
  • Confirm whether installed versions are 1.1 or earlier.
  • Search posts and pages for 'syv' shortcode usage.
  • Review Contributor, Author, Editor, and Administrator account assignments.
  • Monitor WordPress security logs for suspicious content changes.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1825 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2026-1825Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
minorShow YouTube video0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.