Is contentlock (WordPress plugin) vulnerable?

WordPress contentlock has 3 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

3advisories

0critical

0on CISA KEV

0no fix recorded

CVE	Title	Severity	CVSS	Affected	Fixed in
CVE-2024-6022	The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when updating its settings, which could allow attackers to	high	8.8	`<1.0.4`	`1.0.4`
CVE-2024-6023	The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when adding emails, which could allow attackers to make a l	high	8.8	`<1.0.4`	`1.0.4`
CVE-2024-6024	The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when deleting groups or emails, which could allow attackers	high	8.8	`<1.0.4`	`1.0.4`

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.

# one-time install
pip install phpwarden

# then
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.