Confection WordPress Cable 0.4.0–0.4.7: A Settings Value Written Into a PHP File Is Unauthenticated RCE (CVE-2026-115252, CVSS 10.0)

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Confection WordPress Cable 0.4.0–0.4.7: A Settings Value Written Into a PHP File Is Unauthenticated RCE (CVE-2026-115252, CVSS 10.0)

Some vulnerabilities need a long chain. This one needs a settings form. The Confection WordPress Cable plugin, at versions 0.4.0 through 0.4.7, saves its settings without any capability or nonce check — and writes one of those settings, unmodified, into a standalone PHP file that it then serves. Whoever can reach the settings save can put code on the server. No account needed. That is CVE-2026-115252, scored CVSS 10.0 by its assigning CNA. There is no fixed version named in the CVE record yet.

What Happened

CVE-2026-115252 is an unauthenticated remote code execution vulnerability in the Confection WordPress Cable plugin, disclosed November 9, 2026 (CNA: WPScan; GitHub Advisory Database record GHSA-6ch9-px9g-8jxj). It carries two weakness classes, and together they are the whole story: CWE-862, Missing Authorization, and CWE-94, Improper Control of Generation of Code (Code Injection).

Am I Affected?

Check wp-admin → Plugins for the Confection WordPress Cable plugin and its version. At 0.4.0 through 0.4.7, you are in the affected range: an unauthenticated visitor can write code into a file your server executes.

One honesty note, because it is the whole point of how we cover these: our scanner does not claim a version check for this one. The CVE record names no wordpress.org slug for this plugin — no package name, vendor listed as "Unknown" — and no directory listing was verified from a primary source, so no slug is asserted and no install count is quoted here. Keying a readme check to a guessed slug would produce claims we cannot stand behind in either direction. This article exists because the flaw is real and urgent — not because we can detect it passively. What the free mini-scan can do is check the rest of your site's exposed surface while you handle this one by hand.

What To Do Now

  1. Deactivate and remove the plugin until a vendor release names this CVE. There is no patched version to update to yet. A settings save that is not running cannot write PHP files.
  2. Audit the server for PHP files you did not write. This flaw's residue is code on disk: look for recently modified or unfamiliar PHP files, especially outside the plugin's own directory, and for files whose modification times you cannot explain.
  3. Audit administrator accounts. Users → All Users: every Administrator should be a person you can name. A code-execution flaw is exactly the kind that gets quietly converted into persistent access.
  4. If you find a file you cannot explain, treat the site as compromised, not just vulnerable. Removing the plugin closes the door; it does not remove what already came through it.

The Bigger Lesson

A setting is data until code treats it as code. The moment a stored value is written into an executable file, every missing check in front of that save — capability, nonce, sanitization — stops being a settings bug and becomes remote code execution. If any part of your stack writes user-influenced values into files the server runs, that write deserves the same scrutiny as a file upload: who may reach it, and what may the value contain, answered server-side, every time.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the audit finds a stranger.


Running Confection WordPress Cable at 0.4.0–0.4.7? Remove it until a patched release names this CVE, then run the free check at preshipit.com/free-scan — it covers the exposures a scan can see, and articles like this one cover the ones it can't.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report