Ameeba Chat App store presentation
Download Ameeba Chat Today
Ameeba Blog Search

CVE-2025-6238: Open Redirect Vulnerability in AI Engine WordPress Plugin

Ameeba’s Mission: Safeguarding privacy by securing data and communication with our patented anonymization technology.

Overview

A critical vulnerability has been identified in the AI Engine plugin for WordPress that poses a severe security risk to users. This vulnerability, classified as CVE-2025-6238, affects version 2.8.4 of the plugin and enables unauthenticated attackers to exploit an open redirect flaw. This issue is particularly concerning as it potentially allows attackers to compromise systems and leak data by intercepting authorization codes and obtaining access tokens.

Vulnerability Summary

CVE ID: CVE-2025-6238
Severity: High (8.0 CVSS)
Attack Vector: Network
Privileges Required: None
User Interaction: Required
Impact: System compromise, Data leakage

Affected Products

Ameeba Chat Icon Escape the Surveillance Era

Most apps won’t tell you the truth.
They’re part of the problem.

Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.

Ameeba Chat gives you a way out.

  • • No phone number
  • • No email
  • • No personal info
  • • Anonymous aliases
  • • End-to-end encrypted

Chat without a trace.

Product | Affected Versions

AI Engine Plugin for WordPress | 2.8.4

How the Exploit Works

The vulnerability arises from an insecure OAuth implementation in the AI Engine plugin for WordPress. Specifically, the ‘redirect_uri’ parameter lacks validation during the authorization flow. This flaw allows unauthenticated attackers to manipulate the ‘redirect_uri’ parameter to point to an attacker-controlled URI. As a result, attackers can intercept the authorization code and obtain an access token, allowing them potential access to the system or the capability to leak data.

Conceptual Example Code

Below is a conceptual example of how the vulnerability might be exploited using an HTTP request:

GET /oauth2/authorize?response_type=code&client_id=CLIENT_ID&redirect_uri=https://attacker.com HTTP/1.1
Host: vulnerable-wordpress-site.com

In this example, the attacker modifies the ‘redirect_uri’ parameter to redirect the user to ‘attacker.com’ instead of a legitimate URI. This allows the attacker to potentially intercept the authorization code and gain unauthorized access.

Mitigation and Remediation

To mitigate this vulnerability, users are advised to update the AI Engine plugin for WordPress to the patched version 2.8.5, where the OAuth is disabled, and the insecure ‘Meow_MWAI_Labs_OAuth’ class is not loaded. In situations where an immediate update is not possible, using a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can provide temporary protection by blocking malicious redirects. As always, users should stay vigilant and ensure they use trusted networks while accessing their WordPress sites.

Talk freely. Stay anonymous with Ameeba Chat.

Disclaimer:

The information and code presented in this article are provided for educational and defensive cybersecurity purposes only. Any conceptual or pseudocode examples are simplified representations intended to raise awareness and promote secure development and system configuration practices.

Do not use this information to attempt unauthorized access or exploit vulnerabilities on systems that you do not own or have explicit permission to test.

Ameeba and its authors do not endorse or condone malicious behavior and are not responsible for misuse of the content. Always follow ethical hacking guidelines, responsible disclosure practices, and local laws.
Ameeba Chat