CVE-2024-6022: The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when updating its settings, w

Q: How do I fix CVE-2024-6022?

contentlock: upgrade to 1.0.4. Exact commands for each OS are on this page.

Q: Is CVE-2024-6022 being exploited?

CVE-2024-6022 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-6022 affect?

CVE-2024-6022 affects contentlock. Severity is high (CVSS 8.8). The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

Q: How urgent is CVE-2024-6022?

Priority 42/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2024-6022 is a high-severity flaw (CVSS 8.8) affecting contentlock. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-352
Published	2024-07-12
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: adamsolymosi

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-07-12 06:15 UTCPublished CVE record published
2026-06-17 08:17 UTCUpdated Record last modified

adamsolymosi contentlock UPGRADE

Affected: < 1.0.4

Fixed in: 1.0.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy contentlock || rpm -q contentlock || contentlock --version

2. UPGRADE to 1.0.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade contentlock

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade contentlock

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-6022?

contentlock: upgrade to 1.0.4. Exact commands for each OS are on this page.

Is CVE-2024-6022 being exploited?

CVE-2024-6022 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-6022 affect?

CVE-2024-6022 affects contentlock. Severity is high (CVSS 8.8). The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

How urgent is CVE-2024-6022?

Priority 42/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-6024 HIGH 8.8 UPGRADE The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when deleting groups or email
CVE-2024-6023 HIGH 8.8 UPGRADE The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when adding emails, which cou

References

← Back to latest CVEs