CVE-2025-9952 json
Trinity Audio <= 5.20.2 - Reflected Cross-Site Scripting
published last yr. modified 29d ago also EUVD-2025-32407
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 20%
- public exploits
- 0
- none known
Summary
The Trinity Audio – Text to Speech AI audio player to convert content into audio plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'range-date' parameter in all versions up to, and including, 5.20.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
Is CVE-2025-9952 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected products
- sergiotrinity Trinity Audio – Text to Speech AI audio player to convert content into audio
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/a68ca792-6870-4e28-b118-ee1125842955?source=cve
- plugins.trac.wordpress.org /browser/trinity-audio/tags/5.20.1/admin/inc/post-management.php#L44
- plugins.trac.wordpress.org /browser/trinity-audio/tags/5.20.1/admin/inc/post-management.php#L37
- plugins.trac.wordpress.org /changeset/3371934/trinity-audio/trunk/admin/inc/post-management.php
Sources
- CVE List CVE-2025-9952
- NVD CVE-2025-9952
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.