ContentLock
contentlock · plugin
Known security vulnerabilities for ContentLock. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
3 exploitable without logging in · latest Jul 12, 2024
Before you install
Known vulnerabilities fixed
- A fixed release exists for all 3 known records (latest 1.0.6).
Install the current version and keep it updated.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 1.0.6 · last updated Mar 24, 2025
wordpress.org status checked on Oct 19, 2026
Vulnerabilities
- High 8.8
CVE-2024-6024unauthenticated · needs a click≤ 1.0.3
ContentLock <= 1.0.3 - Groups/Emails Deletion via CSRF
- High 8.8
CVE-2024-6023unauthenticated · needs a click≤ 1.0.3
ContentLock <= 1.0.3 - Email Adding via CSRF
- High 8.8
CVE-2024-6022unauthenticated · needs a click≤ 1.0.3
ContentLock <= 1.0.3 - Settings Update via CSRF
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).