CVE-2025-6238: AI Engine 2.8.4 - Insecure OAuth Implementation
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 'redirecturi' 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 'MeowMWAILabsOAuth' class is not loaded in the plugin in the patched version 2.8.5.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
AI Engine plugin for WordPressto a version that resolves this vulnerability.Fixed in 2.8.5 - Configuration
Ensure the OAuth authorization flow validates the 'redirect_uri' parameter before use, since in v2.8.4 it is missing validation.
AI Engine plugin for WordPress redirect_uri validation (OAuth authorization flow) = validated
Event History
Frequently Asked Questions
What is the severity of CVE-2025-6238?
CVE-2025-6238 has a high severity rating due to the potential for unauthenticated attackers to exploit the open redirect vulnerability.
How do I fix CVE-2025-6238?
To fix CVE-2025-6238, update the AI Engine plugin for WordPress to the most recent version that addresses the vulnerable OAuth implementation.
Who is affected by CVE-2025-6238?
Users of the AI Engine plugin for WordPress version 2.8.4 are specifically affected by CVE-2025-6238.
What kind of attacks can CVE-2025-6238 enable?
CVE-2025-6238 can enable attacks such as phishing attempts through open redirects that can deceive users.
Is there a workaround for CVE-2025-6238?
A temporary workaround for CVE-2025-6238 is to disable the AI Engine plugin until a patch can be applied.