dbcve.org
CloudflareWordPress extension

CVE-2024-0212

MEDIUM · 6.5 CVSS v3.1 Published 2024-01-29
Fix available
A fix is available. Upgrade to 4.12.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Cloudflare WordPress plugin contains an improper authentication vulnerability where certain API endpoints lack proper capability checks. This allows authenticated users with low-level privileges (such as WordPress Subscribers) to make Cloudflare API calls and access data they should not have permission to view, effectively bypassing authorization controls.

MitigationUpdate the Cloudflare WordPress plugin to the latest version which implements proper authentication and capability checks on all API endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CloudflareWordPress extension
Affected:< 4.12.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Cloudflare plugin is installed
    Log in to WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Cloudflare' in the list of active plugins.
    Affected if The Cloudflare WordPress plugin appears in the installed plugins list.
  2. Check the installed version number
    In the WordPress admin, go to Plugins > Installed Plugins. Find the Cloudflare plugin and note the version number displayed beneath the plugin name.
    Affected if The installed version is lower than 4.12.3 (for example, 4.12.0, 4.11.0, or any version number less than 4.12.3).
  3. Confirm presence of low-privilege user accounts
    In WordPress admin, go to Users > All Users. Review the list of registered users and their assigned roles. Look for users with the 'Subscriber' role or any other low-privilege role.
    Affected if There exists at least one user account with Subscriber-level privileges or lower.
  4. Test API endpoint accessibility with low-privilege account
    Using a low-privilege user account (such as a Subscriber), attempt to access Cloudflare-related API endpoints. These are typically found under wp-admin/admin-ajax.php or wp-json/cloudflare/ routes. Send a request and observe the response.
    Affected if The API endpoint returns successful data or performs actions without returning a 401 (Unauthorized) or 403 (Forbidden) error.

A user is affected if they have the Cloudflare WordPress plugin installed at a version below 4.12.3 AND have at least one low-privilege user account (Subscriber role) on their WordPress site, allowing unauthorized API access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.12.3 or later
Fixed in 4.12.3
Interim mitigation

Update the Cloudflare WordPress plugin to the latest version which implements proper authentication and capability checks on all API endpoints.

Recommended fix High confidence

4.12.3

  1. Update the Cloudflare WordPress plugin to version 4.12.3 or later via the WordPress admin dashboard (Plugins > Updates), or via wp-cli: wp plugin update cloudflare

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloudflare Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0212 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data