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

CVE-2026-9125

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-12
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 Presto Player plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'link_url' parameter of the [presto_player_overlay] shortcode in versions up to, and including, 4.2.0 This is due to insufficient input sanitization and output escaping in the getOverlays() function, which copies the link_url shortcode attribute directly into the overlay configuration without scheme validation, allowing javascript: URIs to survive and be rendered as the href of a clickable anchor element by the presto-dynamic-overlay-ui web component. 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 Presto Player WordPress plugin fails to properly sanitize and validate the link_url parameter in the [presto_player_overlay] shortcode. The getOverlays() function copies the user-supplied link_url directly into overlay configuration without checking for dangerous URL schemes like javascript:, which then gets rendered as an anchor href by the presto-dynamic-overlay-ui web component, executing stored XSS.

MitigationImplement strict input sanitization for the link_url parameter to whitelist only safe URL schemes (http, https) and reject javascript: or other dangerous protocols. Additionally, apply proper output escaping when rendering the link in the web component.

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 Presto Player plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Presto Player' in the list. Alternatively, check the /wp-content/plugins/ directory for a presto-player folder.
    Affected if Plugin is not installed means not affected; if installed, continue to next checks.
  2. Identify the installed plugin version
    In WordPress admin > Plugins, click on the Presto Player plugin to view its details, or inspect the plugin's main PHP file (usually presto-player.php) for a 'Version' comment or $version variable.
    Affected if Unable to determine version from plugin files means check manually for vulnerable code patterns.
  3. Locate use of [presto_player_overlay] shortcode
    Search WordPress database for posts/pages containing '[presto_player_overlay]' using phpMyAdmin query: SELECT * FROM wp_posts WHERE post_content LIKE '%presto_player_overlay%'; or use a plugin like Search Regex.
    Affected if No shortcode usage found means not affected; if found, inspect the link_url parameter.
  4. Inspect link_url parameter for dangerous schemes
    Examine the shortcode attributes in post content for link_url='javascript:...' or link_url="javascript:..." patterns. Extract the full shortcode to inspect the link_url value.
    Affected if link_url contains javascript: or other non-http(s) URL schemes indicates vulnerability is exploitable.
  5. Verify web component renders the overlay
    View a page with the overlay in a browser, right-click > Inspect, and look for the presto-dynamic-overlay-ui web component in the DOM. Check anchor tags for href attributes containing javascript:
    Affected if Anchor href contains javascript: scheme when rendered means the stored XSS is present and executable.

User is affected if Presto Player plugin is installed AND the [presto_player_overlay] shortcode is in use with a link_url parameter containing javascript: or other dangerous URL schemes that get rendered by the web component.

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

Implement strict input sanitization for the link_url parameter to whitelist only safe URL schemes (http, https) and reject javascript: or other dangerous protocols. Additionally, apply proper output escaping when rendering the link in the web component.

Recommended fix Low confidence

4.2.1 or later (any version > 4.2.0)

  1. 1. Update the Presto Player WordPress plugin to the latest available version (4.2.1 or later) via the WordPress plugin repository, or
  2. 2. If automatic updates are enabled, verify that the plugin has been updated to version 4.2.1 or newer in the Plugins admin panel
  3. 3. Confirm the update was successful by checking the plugin version number

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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