# CVE-2026-92424: Content Egg < 11.9.0 - Contributor+ Stored XSS via Import Queue

> Contributors can inject stored XSS via the import queue, executing scripts in the context of privileged users viewing the content.

- **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:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-f6mm-vhgg-jr4m

## What is CVE-2026-92424?

CVE-2026-92424 is a medium-severity cross-site scripting vulnerability in Unknown Content Egg, published on 30 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 Content Egg  WordPress plugin before 11.9.0 does not verify that a user running its bulk content-import feature is authorized for the import preset they select, and switches to the preset author's identity before creating the resulting post, allowing users with contributor-level access and above to store arbitrary web scripts unfiltered under a privileged user's account, executing in the context of anyone who later views that content.

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

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


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

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

## Is CVE-2026-92424 being exploited?

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

Public exploit code:

- https://github.com/aymencdm/cve-2026-92424-content-egg-stored-xss- (github_poc): https://github.com/aymencdm/cve-2026-92424-content-egg-stored-xss-

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92424 is a medium-severity cross-site scripting vulnerability in Unknown Content Egg, published on 30 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-92424 in the wild and no public exploit code.

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

## Sources

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

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