Contentlock

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:unknown:contentlock:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorUnknown (668ca391-a6cc-5e33-879b-83885214de33)
ProductContentlock (5f9d3ee3-1b9c-5401-a932-5a1af8088ff4)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-6024 vulnerable 2026-06-08 06:58:17.233218 ContentLock <= 1.0.3 - Groups/Emails Deletion via CSRF
The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when deleting groups or emails, which could allow attackers to make a logged in admin remove them via a CSRF attack
Published: 2024-07-12T06:00:07.258Z
Updated: 2024-08-01T21:25:03.203Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-6023 vulnerable 2026-06-08 06:58:17.229162 ContentLock <= 1.0.3 - Email Adding via CSRF
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 logged in admin perform such action via a CSRF attack
Published: 2024-07-12T06:00:06.958Z
Updated: 2024-08-01T21:25:03.160Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-6022 vulnerable 2026-06-08 06:58:17.227745 ContentLock <= 1.0.3 - Settings Update via CSRF
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
Published: 2024-07-12T06:00:06.639Z
Updated: 2024-08-01T21:25:03.198Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.