# CVE-2026-10755: All in One SEO < 4.9.9 – Contributor+ Incorrect Authorization via AI Integration

> Contributors can overwrite site-wide AI integration settings due to missing authorization checks in the All in One SEO WordPress plugin.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-8hj6-5c8v-39ff

## What is CVE-2026-10755?

CVE-2026-10755 is a low-severity missing authorization vulnerability in Unknown All in One SEO, published on 20 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The All in One SEO  WordPress plugin before 4.9.9 does not correctly restrict access to some of its AI integration REST API endpoints, allowing users with low-level privileges such as Contributors to overwrite or reset the site-wide AI integration state.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-10755 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10755 is a low-severity missing authorization vulnerability in Unknown All in One SEO, published on 20 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10755 exists.

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

## Sources

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

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