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

CVE-2026-3299

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-16
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 WP YouTube Lyte plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'lyte' shortcode in all versions up to, and including, 1.7.29 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 WP YouTube Lyte WordPress plugin up to version 1.7.29 contains a stored XSS vulnerability in its 'lyte' shortcode. Authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript via shortcode attributes due to insufficient input sanitization and lack of output escaping, causing scripts to execute when users view affected pages.

MitigationUpdate WP YouTube Lyte to version 1.7.30 or later which implements proper input sanitization and output escaping on shortcode attributes. Alternatively, restrict contributor-level user permissions until the patch is applied.

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. Verify WP YouTube Lyte plugin is installed and active
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP YouTube Lyte' in the list. Confirm it shows as 'Active'.
    Affected if Plugin is not installed or is not active (not vulnerable in this case)
  2. Check the installed plugin version
    Click on the plugin name in the WordPress plugins list to view details, or inspect the plugin header in wp-content/plugins/lyte/lyte.php to find the 'Version' field. Compare against the affected range: versions 1.7.29 and below.
    Affected if Installed version is 1.7.29 or lower
  3. Identify pages or posts using the lyte shortcode
    Search your WordPress database: run a query on wp_posts for content containing '[lyte' or use a plugin like 'Search Regex' to scan post content for the shortcode pattern.
    Affected if The lyte shortcode is present in any published post, page, or custom post type content
  4. Review user role permissions for contributor-level accounts
    Go to WordPress admin > Users > Roles, or inspect wp_usermeta and wp_roles tables to identify users with 'contributor' role or higher who can create or edit content.
    Affected if There are user accounts with contributor-level or higher access who did not create the content themselves (potential attacker)
  5. Inspect shortcode attributes in existing content for unsanitized input
    Manually review posts containing [lyte] shortcode. Check if any attributes like 'url', 'id', or other parameters contain unusual characters or script tags that were not escaped.
    Affected if Shortcode attributes contain raw user input without proper encoding (visible injection attempt)

Your environment is affected if WP YouTube Lyte version 1.7.29 or earlier is active AND the lyte shortcode is used on your site AND untrusted users have contributor-level access or higher.

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 WP YouTube Lyte to version 1.7.30 or later which implements proper input sanitization and output escaping on shortcode attributes. Alternatively, restrict contributor-level user permissions until the patch is applied.

Recommended fix Moderate confidence

1.7.30

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find WP YouTube Lyte in the plugin list
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload the updated plugin file from wordpress.org/plugins/wp-youtube-lyte

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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