Content Egg · Security record

Is Content Egg safe?

No known vulnerability affects the current version (12.1.0). 10 issues were found in earlier versions and fixed, the latest disclosed on Oct 29, 2026.

Checked 3 days ago against the WPVulnerability database, for version 12.1.0.

How it’s looked after

Last release: Oct 29, 2026 (1 week ago)
Releases in the last year: 14
Tested up to: WordPress 7.1.4
Support resolved: 1 of 1 threads in two months
Active installs: 10K+

10 known vulnerabilities

3 high
4 medium
3 not rated

None affects the current version.

Disclosed each year

20222
20231
20251
20265

Every known vulnerability in Content Egg

Newest first, with any that affect the current version at the top.

medium
Missing Authorization to Authenticated (Contributor+) Arbitrary Post Meta Modification via 'post_id' Parameter via cegg_update_products AJAX Action
Fixed in 12.1.0 · CVE-2026-119059 · Oct 29, 2026 · Wordfence
medium
Missing Authorization to Authenticated (Author+) Administrator-Authored Post Creation via 'preset_id' Parameter
Fixed in 12.1.0 · CVE-2026-119087 · Oct 29, 2026 · Wordfence
Cross-site Scripting
Fixed in 11.9.0 · CVE-2026-92424 · Sep 30, 2026 · CVE
high
Authenticated (Shop Manager+) PHP Object Injection
Fixed in 11.9.0 · CVE-2026-96832 · Aug 4, 2026 · Wordfence
high
Authenticated (Author+) Arbitrary File Deletion
Fixed in 11.4.0 · CVE-2026-15979 · Aug 4, 2026 · Wordfence
high
Authenticated (Editor+) PHP Object Injection
Fixed in 8.0.0 · CVE-2025-47536 · Jul 30, 2025 · Wordfence
WordPress Content Egg Plugin <= 5.3.0 is vulnerable to Cross Site Scripting (XSS)
Fixed in 5.3.1 · Apr 25, 2023 · Patchstack
medium
Cross-Site Request Forgery
Fixed in 5.5.0 · CVE-2022-25952 · Oct 31, 2022 · Wordfence
medium
Reflected Cross-Site Scripting
Fixed in 5.3.0 · CVE-2022-0428 · Apr 4, 2022 · Wordfence
Reflected Cross-Site Scripting
Fixed in 5.3.1 · WPScan

Questions about Content Egg’s security

Is Content Egg safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Content Egg updated: most attacks target sites that haven’t updated.

Does Content Egg have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 10 older issues, fixed in earlier versions, so keep Content Egg up to date.

Is Content Egg still maintained?

Yes. Its last release was 1 week ago. Its authors resolved 1 of the 1 support threads opened in the last two months.

Is Content Egg compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.1.4, the current version.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.