# CVE-2026-110982: AI Engine < 3.8.6 - Editor+ Arbitrary Post Title and Excerpt Update via update_post_title and update_post_excerpt


- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-7phx-x376-59jf

## What is CVE-2026-110982?

CVE-2026-110982 is a medium-severity vulnerability in Unknown AI Engine, published on 21 Oct 2026. 

### Official description

The AI Engine  WordPress plugin before 3.8.6 does not check that the caller is allowed to edit the targeted object before updating its title and excerpt, allowing users with the Editor role and above to modify arbitrary posts of any type, including content they cannot otherwise edit such as navigation menus, block templates, global styles and WooCommerce coupons.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-110982 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110982 is a medium-severity vulnerability in Unknown AI Engine, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110982 in the wild and no public exploit code.

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

## Sources

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

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