WordPress plugin · Updated daily · Source: Wordfence Intelligence

Content Egg vulnerabilities: affected versions and fixes

Content Egg has 10,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Content Egg at a glance

  • 9 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Nov 5, 2026.
  • Ranked #1945 by popularity on WordPress.org (10,000+ active installs).
  • The latest version is 12.1.0 (released Oct 29, 2026). The most recent security fix shipped in 12.1.0.
  • 1 vulnerability has no fix yet. Check the list below to see whether it affects how you use the plugin.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Content Egg version

Enter the Content Egg version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Content Egg”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Content Egg”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (12.1.0). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Content Egg vulnerabilities

  • Content Egg – Affiliate Product Importer & Price Comparison <= 12.0.0 - Unauthenticated Information Exposure

    Information disclosure · CVE-2026-119751

    Affected versions: ≤ 12.0.0

    Fixed in: No fix yet

    Severity: Medium 5.3 · Disclosed Nov 5, 2026

  • Content Egg <= 12.0.0 - Missing Authorization to Authenticated (Contributor+) Arbitrary Post Meta Modification via 'post_id' Parameter via cegg_update_products AJAX Action

    Missing authorization · CVE-2026-119059

    Affected versions: ≤ 12.0.0

    Fixed in: 12.1.0

    Severity: Medium 4.3 · Disclosed Oct 29, 2026

  • Content Egg <= 12.0.0 - Missing Authorization to Authenticated (Author+) Administrator-Authored Post Creation via 'preset_id' Parameter

    Missing authorization · CVE-2026-119087

    Affected versions: ≤ 12.0.0

    Fixed in: 12.1.0

    Severity: Medium 4.3 · Disclosed Oct 29, 2026

  • Content Egg <= 11.8.0 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-92424

    Affected versions: ≤ 11.8.0

    Fixed in: 11.9.0

    Severity: Medium 6.4 · Disclosed Sep 28, 2026

  • Content Egg – Affiliate Product Importer & Price Comparison <= 6.3.1 - Authenticated (Shop Manager+) PHP Object Injection

    PHP object injection · CVE-2026-96832

    Affected versions: ≤ 6.3.1

    Fixed in: 11.9.0

    Severity: Medium 6.6 · Disclosed Sep 28, 2026

  • Content Egg <= 11.3.0 - Authenticated (Author+) Arbitrary File Deletion

    Arbitrary file read or deletion · CVE-2026-15979

    Affected versions: ≤ 11.3.0

    Fixed in: 11.4.0

    Severity: High 8.1 · Disclosed Aug 4, 2026

  • Content Egg <= 7.0.0 - Authenticated (Editor+) PHP Object Injection

    PHP object injection · CVE-2025-47536

    Affected versions: ≤ 7.0.0

    Fixed in: 8.0.0

    Severity: Medium 6.6 · Disclosed Jul 30, 2025

  • Content Egg <= 5.4.0 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2022-25952

    Affected versions: ≤ 5.4.0

    Fixed in: 5.5.0

    Severity: High 8.8 · Disclosed Oct 31, 2022

  • Content Egg <= 5.3.0 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2022-0428

    Affected versions: < 5.3.0

    Fixed in: 5.3.0

    Severity: Medium 6.1 · Disclosed Apr 6, 2022

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 5, 2026.

Most common weaknesses in Content Egg

Missing authorization

2 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Cross-site scripting (XSS)

2 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

PHP object injection

2 issues

Specially crafted data makes the server behave in unintended ways. Combined with the right conditions, it can lead to a full takeover.

Frequently asked questions

Is Content Egg safe to use?

Content Egg is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (12.1.0) and turn on automatic updates. That said, 1 issue has no fix yet, so check the list below.

How do I find which version of Content Egg my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesContent Egg on WordPress.org