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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| — | Content Egg | < 11.9.0 | 11.9.0 |
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
Third-party code, not reviewed by us. Public PoCs are sometimes fake or contain malware. Read the code first and run it only in an isolated lab, against systems you are authorised to test.
GitHub 1 repository
-
aymencdm/cve-2026-92424-content-egg-stored-xss- ★ 0 · Oct 29, 2026
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
References
- https://wpscan.com/vulnerability/917b8042-b38c-4b6a-9237-1dd08ada157d/ exploit vdb-entry technical-description