CVE-2025-9196
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Trinity Audio – Text to Speech AI audio player to convert content into audio plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.21.0 via the ~/admin/inc/phpinfo.php file that gets created on install. This makes it possible for unauthenticated attackers to extract sensitive data including configuration data.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Trinity Audio WordPress plugin creates a phpinfo.php file in ~/admin/inc/ during installation that remains publicly accessible. This file exposes sensitive server configuration details, environment variables, and PHP settings to unauthenticated attackers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Trinity Audio plugin installationCheck the WordPress plugins directory for the Trinity Audio plugin folder (typically wp-content/plugins/trinity-audio or similar)Affected if The Trinity Audio plugin is installed on the WordPress site
-
Locate the phpinfo.php fileCheck for the presence of phpinfo.php in the ~/admin/inc/ subdirectory within the plugin folderAffected if The file phpinfo.php exists in the admin/inc/ directory of the Trinity Audio plugin
-
Verify public accessibilityAttempt to access the file via HTTP request (e.g., visit yoursite.com/wp-content/plugins/[trinity-audio]/admin/inc/phpinfo.php) without authenticationAffected if The phpinfo.php file returns PHP configuration information and is accessible without login credentials
-
Check for sensitive information exposureIf accessible, verify the page output contains PHP version, server environment details, loaded extensions, and configuration valuesAffected if The page displays phpinfo() output with server configuration and environment variables
You are affected if the Trinity Audio plugin is installed and the phpinfo.php file in its admin/inc/ directory is publicly accessible, exposing server configuration details.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the plugin to a patched version once released, or manually remove the exposed phpinfo.php file from the ~/admin/inc/ directory and restrict access to sensitive admin directories via .htaccess rules.
5.21.1 or latest available version
- Check if a newer version of the Trinity Audio plugin is available in the WordPress plugin repository
- If version 5.21.1 or higher is available, navigate to Plugins > All Plugins in WordPress admin
- Update the Trinity Audio plugin to the latest available version
- Alternatively, if update is not available, manually delete the ~/admin/inc/phpinfo.php file from the plugin directory via FTP or file manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9196 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data