CVE-2026-92424: Content Egg (WordPress plugin) · Cross-Site Scripting (XSS)
Affects Content Egg (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.8 Medium : upgrade to 11.9.0 when convenient.
Data as of 13 Nov 2026, 23:54 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 11.9.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade Content Egg (WordPress plugin) to 11.9.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Content Egg | Affected
| Fixed in
|
AI-suggested
A fix is available in Content Egg version 11.9.0. Users should upgrade to version 11.9.0 or later to remediate this vulnerability. Until patched, restrict contributor-level access to trusted users and avoid using the bulk content-import feature with untrusted presets.
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.