Description
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.
References10
- plugins.trac.wordpress.org/browser/presto-player/tags/4.1.1/dis…
- plugins.trac.wordpress.org/browser/presto-player/tags/4.1.1/inc…
- plugins.trac.wordpress.org/browser/presto-player/tags/4.1.1/inc…
- plugins.trac.wordpress.org/browser/presto-player/tags/4.1.1/tem…
- plugins.trac.wordpress.org/browser/presto-player/tags/4.1.4/dis…
- plugins.trac.wordpress.org/browser/presto-player/tags/4.1.4/inc…
- plugins.trac.wordpress.org/browser/presto-player/tags/4.1.4/inc…
- plugins.trac.wordpress.org/browser/presto-player/tags/4.1.4/tem…
- plugins.trac.wordpress.org/changeset/3553268/presto-player/trun…
- research.cleantalk.org/cve-2026-9125/
Metrics
- CVSS 3.1
-
6.4
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N - EPSS — exploit probability
- 0% percentile: 30 · as of 16 November 2026
- CWE
- CWE-79
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.