Widget Options ≤ 4.2.6.1: Two Parsers Disagree, and the Difference Is eval() (CVE-2026-116615, CVSS 8.8)

Running Widget Options on your site? Check it against CVE-2026-116615 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Widget Options is in the affected range (≤ 4.2.6.1), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Widget Options ≤ 4.2.6.1: Two Parsers Disagree, and the Difference Is eval() (CVE-2026-116615, CVSS 8.8)

One parser strips the dangerous part. Another parser puts it back together — and hands it to @eval. The filter and the renderer in the Widget Options plugin read the same block comment in two different ways, and the gap between those readings is a code-injection flaw that runs on every front-end page view. That is CVE-2026-116615, scoring CVSS 8.8, disclosed November 13, 2026 (CNA: Wordfence).

What Happened

CVE-2026-116615 is an authenticated code injection vulnerability in the Widget Options plugin (wordpress.org slug widget-options, 100,000+ active installs).

Am I Affected?

Check wp-admin → Plugins for Widget Options and its version. At 4.2.6.1 or below, your site runs the affected code. The sites with real exposure are the ones that hand out Author or Contributor accounts they do not fully control — multi-author blogs, membership and community sites, and any site where contributors submit posts for publication.

Our scanner checks it: run the free mini-scan, or check just this plugin at /tools/plugin-check?slug=widget-options. The check reads the version your site announces and flags anything at 4.2.6.1 or below. A version above that range earns no strength and no clean bill from this check, because the CVE record names no patched version — silence is the honest answer there. The check never creates or publishes content — it reads the public version disclosure only.

What To Do Now

  1. Update Widget Options to the newest available release today, and confirm in the vendor changelog that the block-logic handling changed.
  2. Audit Author and Contributor accounts. Look for accounts you do not recognize, and for recently published posts and blocks whose content you cannot account for — a planted block is this flaw's payload vehicle.
  3. Review pending Contributor submissions before publishing them. Until you have updated, a submission is exactly the path this flaw uses to reach the render side.

The Bigger Lesson

A sanitizer and a renderer that parse the same input differently are a vulnerability waiting for a payload. Stripping is only a control if the thing being stripped is read the same way by the code that later renders it — strip and render must share one parser, or the difference between them becomes the exploit.

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 account audit finds something you do not recognize.


Running Widget Options on a multi-author site? Update to the newest release today, audit your author-level accounts, then run the free check at preshipit.com/free-scan — our scanner checks it, version-checking this plugin against CVE-2026-116615 from the version your site announces to the world.

Check Widget Options on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls Widget Options's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-116615 included. No scan, no account.

Open the free plugin checker →

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.

Running Widget Options on your site? Check it against CVE-2026-116615 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Widget Options is in the affected range (≤ 4.2.6.1), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. 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