CVE-2025-9886

Trinity Audio <= 5.20.2 - Cross-Site Request Forgery

2025-10-03 00:00
Moose Love

Strategic Overview

Status
Patched in 5.21.0
Affected Version
<= 5.20.2
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-9886
View all Trinity Audio – Text to Speech AI audio player to convert content into audio vulnerabilities

At a glance

CVE-2025-9886 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Trinity Audio WordPress plugin, affecting versions <= 5.20.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.21.0; sites on affected versions should update now. Disclosed October 2025, reported by Moose Love.

Vulnerability Overview

The Trinity Audio – Text to Speech AI audio player to convert content into audio plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.20.2. This is due to missing or incorrect nonce validation in the '/admin/inc/post-management.php' file. This makes it possible for unauthenticated attackers to activate/deactivate posts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Trinity Audio <= 5.20.2 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Trinity Audio the fix is 5.21.0: builds <= 5.20.2 are affected, anything from 5.21.0 onward is not.

Remediation

Update to version 5.21.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Trinity Audio: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Trinity Audio 5.21.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C