Stored cross-site scripting in Presto Player WordPress plugin
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-79.
Summary
The Presto Player plugin for WordPress is affected in all versions up to and including 4.5.1. Insufficient input sanitization and output escaping let unauthenticated attackers store arbitrary web scripts in comment content through the presto-player tag (CWE-79). The scripts run when a user opens an affected page, and an attacker can wait for WordPress to auto-approve later comments from the same author before injecting the payload without admin action.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Description from the CNA
The Presto Player plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via <presto-player> Tag in all versions up to, and including, 4.5.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires an initial comment approval, though WordPress default settings will auto-approve all subsequent comments from the same author, allowing a patient unauthenticated attacker to land the payload without further admin intervention.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| 2winfactor | Presto Player | up to 4.5.1 | — | No fix listed | CNA |
- Presto Player Vendor2winfactor Affected up to 4.5.1 Fixed in — No fix listed CNA
Remediation
The sources list no fixed version for Presto Player.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Timeline
- 2026-10-10 Threatist record created from CVE-2026-96682
- 2026-10-10 Alias added: GHSA-rg8w-j32p-wvqw
- 2026-10-11 CISA SSVC decision points changed
- 2026-10-11 Priority changed: MEDIUM → LOW
References
Other 6
- https://www.wordfence.com/threat-intel/vulnerabilities/id/c5bfa589-c9ee-40bb-ad41-36ff86030e30?source=cve
- https://plugins.trac.wordpress.org/browser/presto-player/tags/4.5.1/inc/Services/Compatibility.php#L18
- https://plugins.trac.wordpress.org/browser/presto-player/tags/4.5.1/inc/Services/Compatibility.php#L58
- https://plugins.trac.wordpress.org/browser/presto-player/tags/4.5.1/dist/components/web-components/p-6d7bec14.entry.js
- https://plugins.trac.wordpress.org/browser/presto-player/tags/4.5.1/inc/Services/Scripts.php#L439
- https://plugins.trac.wordpress.org/changeset?reponame=&new=3712507%40presto-player%2Ftags%2F4.5.2&old=3697985%40presto-player%2Ftags%2F4.5.1
More 2winfactor vulnerabilities
- TI-2026-08022 Cross-site scripting in 2winfactor Presto Player CVSS 3.1MEDIUM 6.4
Sources
- CVE-2026-96682 · CVE Program
- CVE-2026-96682 · NVD
- FIRST EPSS
- GHSA-rg8w-j32p-wvqw · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences