dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-7780

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
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 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 confidence

The AI Engine plugin for WordPress versions up to 2.9.4 contain a sensitive information exposure vulnerability in the simpleTranscribeAudio endpoint. The endpoint fails to restrict URL schemes before calling get_audio(), allowing authenticated attackers with Subscriber-level access to supply malicious URLs (e.g., file://) to read arbitrary files from the server filesystem and exfiltrate the contents via the plugin's OpenAI API integration.

MitigationUpdate the AI Engine plugin to version 2.9.5 or later which includes proper URL scheme validation. If immediate update is not possible, consider restricting access to the simpleTranscribeAudio endpoint or disabling the OpenAI transcription functionality as a temporary measure.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify AI Engine plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'AI Engine'. Check the version number displayed, or inspect the plugin file header in wp-content/plugins/ai-engine/ai-engine.php
    Affected if The installed version is 2.9.4 or lower
  2. Confirm simpleTranscribeAudio endpoint exists
    Check if the file containing simpleTranscribeAudio exists in the plugin directory, typically in includes/rest/endpoints.php or similar. Alternatively, attempt a POST request to /wp-json/ai-engine/v1/transcribe (authenticated as a subscriber or higher)
    Affected if The endpoint is accessible and responds to requests
  3. Check OpenAI API configuration
    Navigate to WordPress admin > AI Engine settings > API Keys tab. Verify if an OpenAI API key is saved in the plugin configuration
    Affected if An OpenAI API key is configured and saved in the plugin settings (required for the exfiltration mechanism)
  4. Verify Subscriber role access
    In WordPress admin, go to Users > Users List. Check if any users exist with the Subscriber role, or verify in Users > Roles that the Subscriber role is active
    Affected if Subscriber-level accounts exist on the site (these can trigger the vulnerable endpoint)

You are affected if the AI Engine plugin version is 2.9.4 or lower, the simpleTranscribeAudio endpoint is accessible, and an OpenAI API key is configured in the plugin settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the AI Engine plugin to version 2.9.5 or later which includes proper URL scheme validation. If immediate update is not possible, consider restricting access to the simpleTranscribeAudio endpoint or disabling the OpenAI transcription functionality as a temporary measure.

Recommended fix High confidence

Version 2.9.5 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the AI Engine plugin
  4. Check the current version is 2.9.4 or below
  5. Click Update Now or manually update to the latest available version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7780 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7780 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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