CVE-2025-7780

AI Engine <= 2.9.4 - Missing URL Scheme Validation to Authenticated (Subscriber+) Arbitrary File Read via simpleTranscribeAudio and get_audio Functions

2025-07-23 20:32
ISMAILSHADOW

Strategic Overview

Status
Patched in 2.9.5
Affected Plugin
AI Engine – The Chatbot, AI Framework & MCP for WordPress
Affected Version
<= 2.9.4
CVSS
6.5Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-7780
View all AI Engine – The Chatbot, AI Framework & MCP for WordPress vulnerabilities

At a glance

CVE-2025-7780 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the AI Engine WordPress plugin, affecting versions <= 2.9.4. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.9.5; sites on affected versions should update now. Disclosed July 2025, reported by ISMAILSHADOW.

Vulnerability Overview

The AI Engine plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.9.4. The simpleTranscribeAudio endpoint fails to restrict URL schemes before calling get_audio(). This makes it possible for authenticated attackers, with Subscriber-level access and above, to read any file on the web server and exfiltrate it via the plugin’s OpenAI API integration.

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 interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

AI Engine <= 2.9.4 carries this weakness at get_audio(), and reaching it takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For AI Engine the fix is 2.9.5: builds <= 2.9.4 are affected, anything from 2.9.5 onward is not.

Remediation

Update to version 2.9.5, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: AI Engine 2.9.5 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-7780https://www.wordfence.com/threat-intel/vulnerabilities/id/513274bc-3016-4adb-be78-b13c5fae9c03https://nvd.nist.gov/vuln/detail/CVE-2025-7780

Related records

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