# CVE-2026-82884: All in One SEO < 5.0.0.1 - Contributor+ Stored XSS via ai-assistant Block

> Contributors can inject malicious scripts via the AI assistant block, leading to stored XSS when admins edit posts.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-46w6-gf75-jc42

## What is CVE-2026-82884?

CVE-2026-82884 is a medium-severity cross-site scripting vulnerability in Unknown All in One SEO, published on 2 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The All in One SEO WordPress plugin before 5.0.0.1 does not sanitise and escape some content stored in posts before rendering it back in the post editor, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks that trigger when a higher privileged user edits the post.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-82884 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82884 is a medium-severity cross-site scripting vulnerability in Unknown All in One SEO, published on 2 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-82884 in the wild and no public exploit code.

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

## Sources

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

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