CVE-2025-6238

AI Engine 2.8.4 - Insecure OAuth Implementation

Description

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.

Category

8.0
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.03%
Affected: tigroumeow AI Engine
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2025-6238?
CVE-2025-6238 has been scored as a high severity vulnerability.
How to fix CVE-2025-6238?
To fix CVE-2025-6238, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2025-6238 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2025-6238 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-6238?
CVE-2025-6238 affects tigroumeow AI Engine.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.