HomeWordPress vulnerabilitiesContent Egg
Content Egg vulnerabilities
Content Egg has 4 known vulnerabilities in this database. The most recent published record is dated 30 Sep 2026.
- Known vulnerabilities
- 4
- Active installs
- 10,000+
- Latest version
- 11.9.0
- Last updated
- 23 Sep 2026
- Most recent
- 30 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-92424 | Medium 6.8 | Before 11.9.0 | Fixed in 11.9.0 | 7 d ago |
| Remote code execution CVE-2026-15979 | High 8.1 | Up to 11.3.0 | Fixed in a later version (latest 11.9.0) | 5 Aug 2026 |
| Cross-site request forgery (CSRF) CVE-2022-25952 | Medium 4.3 | Up to 5.4.0 | Fixed in a later version (latest 11.9.0) | 3 Nov 2022 |
| Cross-site scripting (XSS) CVE-2022-0428 | Medium 6.1 | Before 5.3.0 | Fixed in 5.3.0 | 2 May 2022 |
Read the published descriptions
- CVE-2026-92424, 30 Sep 2026
- 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. CVE record
- CVE-2026-15979, 5 Aug 2026
- The Content Egg - Affiliate Product Importer & Price Comparison plugin for WordPress is vulnerable to Arbitrary File Deletion via Path Traversal in versions up to and including 11.3.0. This is due to insufficient validation of the 'img_file' field within the cegg_data post metadata: the value passes only through wp_strip_all_tags() (which does not strip path traversal sequences), is stored directly in post meta, and is later concatenated without normalization into a filesystem path in getFullImgPath() before being passed to PHP's unlink(). This makes it possible for authenticated attackers, with author-level access and above, to delete arbitrary files on the affected site's server which may make remote code execution possible. CVE record
- CVE-2022-25952, 3 Nov 2022
- Cross-Site Request Forgery (CSRF) vulnerability in Keywordrush Content Egg plugin <= 5.4.0 on WordPress. CVE record
- CVE-2022-0428, 2 May 2022
- The Content Egg WordPress plugin before 5.3.0 does not sanitise and escape the page parameter before outputting back in an attribute in the Autoblogging admin dashboard, leading to a Reflected Cross-Site Scripting CVE record
What to do if you run Content Egg
If you run Content Egg, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Content Egg vulnerabilities
Free. We email you when a new vulnerability is published for Content Egg, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.