{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-6238 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6238 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6238 is a high-severity vulnerability in tigroumeow AI Engine, published on 4 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-6238 and fix it if it is affected.\n\nWhat it is: CVE-2025-6238 is a high-severity vulnerability in tigroumeow AI Engine, published on 4 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-6238 in the wild and no public exploit code.\n\nAffected product: tigroumeow AI Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-6238/ (Markdown: https://insights.sbomify.com/CVE-2025-6238/index.md)","id":"CVE-2025-6238","markdown":"https://insights.sbomify.com/CVE-2025-6238/index.md","name":"CVE-2025-6238","record":{"aliases":["GHSA-6wxr-g84w-3h8x"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Unauthenticated attackers can intercept authorization codes and obtain access tokens via an open redirect in the AI Engine WordPress plugin's OAuth flow.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"ai_engine","vendor":"meowapps"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"AI Engine 2.8.4 - Insecure OAuth Implementation","id":"CVE-2025-6238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure","id":"CVE-2025-6239"},"packages":[],"prev":{"headline":"Path Traversal and Arbitrary File Deletion in invoke-ai/invokeai","id":"CVE-2025-6237"},"products":["AI Engine"],"published":"2025-07-04","related":[{"cvss_score":10,"headline":"WordPress AI Engine plugin \u003c= 1.9.98 - Unauthenticated Arbitrary File Upload vulnerability","id":"CVE-2023-51409","kev_date_added":null,"published":"2024-04-12"},{"cvss_score":9.1,"headline":"WordPress AI Engine plugin \u003c= 2.2.63 - Auth. Arbitrary File Upload vulnerability","id":"CVE-2024-34440","kev_date_added":null,"published":"2024-05-13"},{"cvss_score":9.1,"headline":"WordPress AI Engine plugin \u003c= 2.1.4 - Arbitrary File Upload vulnerability","id":"CVE-2024-29100","kev_date_added":null,"published":"2024-03-28"},{"cvss_score":8.8,"headline":"AI Engine 2.8.0 - 2.8.3 - Authenticated (Subscriber+) Insufficient Authorization to Privilege Escalation via MCP","id":"CVE-2025-5071","kev_date_added":null,"published":"2025-06-19"},{"cvss_score":7.2,"headline":"AI-Engine \u003c 2.6.5 - Admin+ SQLi","id":"CVE-2024-10499","kev_date_added":null,"published":"2024-12-12"},{"cvss_score":7.2,"headline":"AI Engine \u003c 2.5.1 - Admin+ RCE","id":"CVE-2024-6451","kev_date_added":null,"published":"2024-08-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-07-08","vendors":["tigroumeow"]},"summary":"Unauthenticated attackers can intercept authorization codes and obtain access tokens via an open redirect in the AI Engine WordPress plugin's OAuth flow.","url":"https://insights.sbomify.com/CVE-2025-6238/"}