# CVE-2023-51409: WordPress AI Engine plugin <= 1.9.98 - Unauthenticated Arbitrary File Upload vulnerability

> Unauthenticated attackers can upload arbitrary files to the AI Engine WordPress plugin, potentially leading to remote code execution.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-c4qr-mpj2-hxhr

## What is CVE-2023-51409?

CVE-2023-51409 is a critical vulnerability in Jordy Meow AI Engine: ChatGPT Chatbot, published on 12 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unrestricted Upload of File with Dangerous Type vulnerability in Jordy Meow AI Engine: ChatGPT Chatbot.This issue affects AI Engine: ChatGPT Chatbot: from n/a through 1.9.98.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2023-51409?

It affects 1 product.


Products: Meowapps Ai Engine.

## How do I fix CVE-2023-51409?

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

## Is CVE-2023-51409 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51409 exists.

Public exploit code:

- AI Engine: ChatGPT Chatbot <= 1.9.98 - Unauthenticated Arbitrary File Upload via rest_upload (github_poc): https://github.com/RandomRobbieBF/CVE-2023-51409
- Unauthenticated 0-click RCE exploit for CVE-2023-51409. Abuses an arbitrary file upload flaw in the AI Engine WordPress plugin to upload a PHP webshell and achieve remote command execution without authentication, including OS detection and an interactive shell. (github_poc): https://github.com/JoshuaProvoste/0-click-RCE-Exploit-for-CVE-2023-51409
- https://github.com/Nxploited/CVE-2023-51409 (github_poc): https://github.com/Nxploited/CVE-2023-51409
- Jordy Meow AI Engine - Unrestricted File Upload (nuclei): http/cves/2023/CVE-2023-51409.yaml

## Other vulnerabilities in Jordy Meow AI Engine: ChatGPT Chatbot

- [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-5071](https://insights.sbomify.com/CVE-2025-5071/): AI Engine 2.8.0 - 2.8.3 - Authenticated (Subscriber+) Insufficient Authorization to Privilege Escalation via MCP (high 8.8)
- [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-2023-51409 and fix it if it is affected.

What it is: CVE-2023-51409 is a critical vulnerability in Jordy Meow AI Engine: ChatGPT Chatbot, published on 12 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51409 exists.

Affected product: Jordy Meow AI Engine: ChatGPT Chatbot. 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-2023-51409/ (Markdown: https://insights.sbomify.com/CVE-2023-51409/index.md)
```

## Sources

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

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