CVE-2025-6238

AI Engine 2.8.4 - Insecure OAuth Implementation

2025-07-03 00:00
István Márton

Strategic Overview

Status
Patched in 2.8.5
Affected Plugin
AI Engine – The Chatbot, AI Framework & MCP for WordPress
Affected Version
2.8.4
CVSS
8.0High
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2025-6238
View all AI Engine – The Chatbot, AI Framework & MCP for WordPress vulnerabilities

At a glance

CVE-2025-6238 is a high-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the AI Engine WordPress plugin, affecting versions 2.8.4. It carries a CVSS score of 8.0 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.8.5; sites on affected versions should update now. Disclosed July 2025, reported by István Márton.

Vulnerability Overview

The AI Engine plugin for WordPress is vulnerable to open redirect in version 2.8.4. This is due to an insecure OAuth implementation, as the 'redirect_uri' parameter is missing validation during the authorization flow. This makes it possible for unauthenticated attackers to intercept the authorization code and obtain an access token by redirecting the user to an attacker-controlled URI. Note: OAuth is disabled, the 'Meow_MWAI_Labs_OAuth' class is not loaded in the plugin in the patched version 2.8.5.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

AI Engine 2.8.4 carries this weakness at redirect_uri, and reaching it takes a caller who can reach the endpoint. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For AI Engine the fix is 2.8.5: builds 2.8.4 are affected, anything from 2.8.5 onward is not.

Remediation

Update to version 2.8.5, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-6238https://www.wordfence.com/threat-intel/vulnerabilities/id/1edc84fd-8cb5-4899-9444-1b6ae3144917https://nvd.nist.gov/vuln/detail/CVE-2025-6238

Related records

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