HomeWordPress vulnerabilitiesPresto Player
Presto Player vulnerabilities
Presto Player has 3 known vulnerabilities in this database. The most recent published record is dated 5 Oct 2026.
- Known vulnerabilities
- 3
- Active installs
- 100,000+
- Latest version
- 4.5.3
- Last updated
- 1 Oct 2026
- Most recent
- 5 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-102914 | Medium 6.5 | Up to 4.5.2 | Fixed in a later version (latest 4.5.3) | 2 d ago |
| Cross-site scripting (XSS) CVE-2026-9125 | Medium 6.4 | Up to 4.2.0 | Fixed in a later version (latest 4.5.3) | 12 Jun 2026 |
| Cross-site scripting (XSS) CVE-2024-2428 | Medium 4.7 | Before 2.2.3 | Fixed in 2.2.3 | 10 Apr 2024 |
Read the published descriptions
- CVE-2026-102914, 5 Oct 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Brainstorm Force Presto Player presto-player allows Stored XSS.This issue affects Presto Player: from n/a through 4.5.2. CVE record
- CVE-2026-9125, 12 Jun 2026
- 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. CVE record
- CVE-2024-2428, 10 Apr 2024
- The Ultimate Video Player For WordPress WordPress plugin before 2.2.3 does not have proper capability check when updating its settings via a REST route, allowing Contributor and above users to update them. Furthermore, due to the lack of escaping in one of the settings, this also allows them to perform Stored XSS attacks CVE record
What to do if you run Presto Player
If you run Presto Player, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Presto Player vulnerabilities
Free. We email you when a new vulnerability is published for Presto Player, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.