Is content-egg (WordPress plugin) vulnerable?

WordPress content-egg has 2 known advisories in the phpwarden feed. Feed 2026.10.29.4, updated 2026-10-29.

2advisories

0critical

0on CISA KEV

1no fix recorded

CVE	Title	Severity	CVSS	Affected	Fixed in
CVE-2022-0428	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	medium	6.1	`<5.3.0`	`5.3.0`
CVE-2022-25952	Cross-Site Request Forgery (CSRF) vulnerability in Keywordrush Content Egg plugin <= 5.4.0 on WordPress.	medium	4.3	`<=5.4.0`	–

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden wordpress /var/www/html

# or, without Composer
pipx install phpwarden   &&   phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs How findings are ranked

A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.