# CVE-2024-0212: Cloudflare WordPress plugin enables information disclosure of Cloudflare API (for low privileged users)

> Low-privileged users can access Cloudflare API data due to improper authentication in the Cloudflare WordPress plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2024
- **Updated:** 6 Jun 2025
- **Also known as:** GHSA-h2fj-7r3m-7gf2

## What is CVE-2024-0212?

CVE-2024-0212 is a high-severity missing authorization vulnerability in Cloudflare-WordPress, published on 29 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Cloudflare Wordpress plugin was found to be vulnerable to improper authentication. The vulnerability enables attackers with a lower privileged account to access data from the Cloudflare API.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-0212?

It affects 1 product.


Products: Cloudflare Cloudflare.

## How do I fix CVE-2024-0212?

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

## Is CVE-2024-0212 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0212 and fix it if it is affected.

What it is: CVE-2024-0212 is a high-severity missing authorization vulnerability in Cloudflare-WordPress, published on 29 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0212 in the wild and no public exploit code.

Affected product: Cloudflare-WordPress. 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-2024-0212/ (Markdown: https://insights.sbomify.com/CVE-2024-0212/index.md)
```

## Sources

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

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