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

> Unauthenticated attackers can modify WP Debugging plugin settings due to missing authorization and CSRF checks in the update function.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Oct 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gpxf-fg24-c2r3

## What is CVE-2021-24779?

CVE-2021-24779 is a medium-severity missing authorization vulnerability in Unknown WP Debugging, published on 25 Oct 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-352 (Cross-Site Request Forgery), CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2021-24779?

It affects 1 product.


Products: Wp Debugging Project Wp Debugging.

## How do I fix CVE-2021-24779?

No fix has been published for CVE-2021-24779 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-24779 being exploited?

There is no known exploitation of CVE-2021-24779 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24779 and fix it if it is affected.

What it is: CVE-2021-24779 is a medium-severity missing authorization vulnerability in Unknown WP Debugging, published on 25 Oct 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-24779 in the wild and no public exploit code.

Affected product: Unknown WP Debugging. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-24779/ (Markdown: https://insights.sbomify.com/CVE-2021-24779/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-24779
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-24779
- OSV: https://osv.dev/vulnerability/CVE-2021-24779

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-24779/
Summaries are generated and may contain mistakes; the official description above is the record.