dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-9860

HIGH · 8.8 CVSS v3.1 Published 2026-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Offload, AI & Optimize with Cloudflare Images plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.10.2 via the 'account-id' parameter parameter. This is due to insufficient privilege enforcement on the cf_images_do_setup AJAX handler, which requires only the upload_files capability (Author+) rather than manage_options before writing to wp-config.php, combined with the absence of single-quote escaping — sanitize_text_field() does not strip single quotes, and filter_input(INPUT_POST) bypasses wp_magic_quotes() slashing — allowing a single quote in the account-id or api-key parameter to break out of the single-quoted PHP string literal in the write_config() define() statement. This makes it possible for authenticated attackers, with author-level access and above, to execute code on the server. This is possible because the 'cf-images-nonce' nonce required by the AJAX handler is exposed to all Author-level and above users on wp-admin/upload.php via the CFImages JavaScript object, meaning any upload-capable user can satisfy the nonce check and reach the vulnerable wp-config.php write path.

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 · high confidence

The Cloudflare Images WordPress plugin has an authenticated RCE vulnerability in versions up to 1.10.2. The cf_images_do_setup AJAX handler only requires upload_files capability (Author+) instead of manage_options, and fails to escape single quotes in the account-id or api-key parameters before writing to wp-config.php. Combined with the exposure of the cf-images-nonce to all upload-capable users via the CFImages JavaScript object on wp-admin/upload.php, attackers can inject PHP code by breaking out of the define() string literal.

MitigationImmediately update to the latest version of the plugin. As a temporary workaround, disable the plugin until a patch is available. Consider reviewing wp-config.php for unauthorized modifications and rotating any exposed API keys.

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

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
High
Availability
High

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

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 Images plugin is installed
    Navigate to WordPress admin Plugins page or check /wp-content/plugins/ directory for cloudflare-images folder
    Affected if Plugin is present in the installation
  2. Check installed plugin version
    View plugin details in WordPress admin Plugins > Installed Plugins page, or read version from plugin's main PHP file header
    Affected if Version is lower than 1.10.3 (or version cannot be determined)
  3. Confirm user role access to AJAX handler
    Check if any user with Author role or higher can access wp-admin/admin-ajax.php?action=cf_images_do_setup, or examine capability requirements in plugin code
    Affected if Non-admin users (Author+) can trigger the AJAX action
  4. Verify account-id parameter is unsanitized
    Examine plugin source code for cf_images_do_setup handler - look for account-id POST parameter usage in define() statements without sanitization
    Affected if The account-id parameter is used directly in PHP define() without escaping single quotes
  5. Check for nonce exposure on upload page
    View source of wp-admin/upload.php while logged in as a user with upload capability, or examine plugin code that enqueues scripts on that page
    Affected if The cf_images_do_setup nonce is visible in page source or output to JavaScript on upload.php

User is affected if Cloudflare Images plugin version is below 1.10.3 and the site has users with Author or higher roles who can access the vulnerable AJAX handler.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately update to the latest version of the plugin. As a temporary workaround, disable the plugin until a patch is available. Consider reviewing wp-config.php for unauthorized modifications and rotating any exposed API keys.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9860 — 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-2026-9860 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