WordPress security by component
Trinity Audio
Plugin description
Trinity Audio is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Dec 09, 2025; the highest CVE/CNA score is 6.1.
Plugin slug:
trinity-audioLatest vulnerability
CVE-2025-67466: Trinity Audio: A security weakness
Trinity Audio is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
| Safe version |
|
||
|---|---|---|---|
| Dec 09, 2025 |
CVE-2025-67466
Trinity Audio: A security weakness
Trinity Audio is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Oct 04, 2025 |
CVE-2025-9952
Trinity Audio – Text to Speech AI audio player to convert content into audio: Cross-site scripting
Trinity Audio – Text to Speech AI audio player to convert content into audio is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.1
NVDPending
|
| Oct 04, 2025 |
CVE-2025-9886
Trinity Audio – Text to Speech AI audio player to convert content into audio: Cross-site request forgery
Trinity Audio – Text to Speech AI audio player to convert content into audio is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Jun 06, 2025 |
CVE-2025-49272
Trinity Audio: A security weakness
Trinity Audio is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVDPending
|