# CVE-2025-5071: AI Engine 2.8.0 - 2.8.3 - Authenticated (Subscriber+) Insufficient Authorization to Privilege Escalation via MCP

> Authenticated subscribers can escalate privileges and modify data via missing capability checks in the AI Engine WordPress plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2025
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-gg23-wpg2-g99p

## What is CVE-2025-5071?

CVE-2025-5071 is a high-severity missing authorization vulnerability in tigroumeow AI Engine, published on 19 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The AI Engine plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to a missing capability check on the 'Meow_MWAI_Labs_MCP::can_access_mcp' function in versions 2.8.0 to 2.8.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to have full access to the MCP and run various commands like 'wp_create_user', 'wp_update_user' and 'wp_update_option', which can be used for privilege escalation, and 'wp_update_post', 'wp_delete_post', 'wp_update_comment' and 'wp_delete_comment', which can be used to edit and delete posts and comments.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-5071?

It affects 1 product.


Products: Meowapps Ai Engine.

## How do I fix CVE-2025-5071?

No fix has been published for CVE-2025-5071 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5071 being exploited?

There is no known exploitation of CVE-2025-5071 in the wild and no public exploit code.

## Other vulnerabilities in tigroumeow AI Engine

- [CVE-2023-51409](https://insights.sbomify.com/CVE-2023-51409/): WordPress AI Engine plugin <= 1.9.98 - Unauthenticated Arbitrary File Upload vulnerability (critical 10.0)
- [CVE-2024-34440](https://insights.sbomify.com/CVE-2024-34440/): WordPress AI Engine plugin <= 2.2.63 - Auth. Arbitrary File Upload vulnerability (critical 9.1)
- [CVE-2024-29100](https://insights.sbomify.com/CVE-2024-29100/): WordPress AI Engine plugin <= 2.1.4 - Arbitrary File Upload vulnerability (critical 9.1)
- [CVE-2025-6238](https://insights.sbomify.com/CVE-2025-6238/): AI Engine 2.8.4 - Insecure OAuth Implementation (high 8.0)
- [CVE-2024-10499](https://insights.sbomify.com/CVE-2024-10499/): AI-Engine < 2.6.5 - Admin+ SQLi (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5071 and fix it if it is affected.

What it is: CVE-2025-5071 is a high-severity missing authorization vulnerability in tigroumeow AI Engine, published on 19 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5071 in the wild and no public exploit code.

Affected product: tigroumeow AI Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5071/ (Markdown: https://insights.sbomify.com/CVE-2025-5071/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5071
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5071
- OSV: https://osv.dev/vulnerability/CVE-2025-5071

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5071/
Summaries are generated and may contain mistakes; the official description above is the record.