# CVE-2026-12510: AI Engine < 3.5.5 - Subscriber+Chatbot Discussion Disclosure and Takeover via IDOR

> Subscribers can read and modify other users' private chatbot conversations due to missing ownership checks in the AI Engine plugin.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **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:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-8rhw-c8ph-cp97

## What is CVE-2026-12510?

CVE-2026-12510 is a medium-severity missing authorization vulnerability in Unknown AI Engine, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The AI Engine  WordPress plugin before 3.5.5 does not verify that a user owns the chatbot conversation referenced by a client-supplied identifier, allowing users with subscriber-level access to read other users' private conversations and take over their conversation records when the discussions feature is enabled.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-12510?


## How do I fix CVE-2026-12510?

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

## Is CVE-2026-12510 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12510 and fix it if it is affected.

What it is: CVE-2026-12510 is a medium-severity missing authorization vulnerability in Unknown AI Engine, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12510 exists.

Affected product: Unknown 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-2026-12510/ (Markdown: https://insights.sbomify.com/CVE-2026-12510/index.md)
```

## Sources

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

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