Notes

Weekly round-up: WordPress 7.1.5, a Nuxt UI XSS fix and custom OIDC in Supabase

WordPress 7.1.5 fixes an unauthenticated route to code execution, Nuxt UI patches a stored XSS, and Supabase adds custom OIDC providers. Plus what I published.

Headless Digital 3 min readroundupwordpressnuxtsupabase

Two security releases worth acting on this week, one in WordPress and one in Nuxt UI, plus a useful auth addition in Supabase.

WordPress 7.1.5 is a serious security release

WordPress 7.1.5 shipped on 18 November with around 20 security fixes, and the release post says to update immediately. I agree. The headline issue is an unauthenticated privilege escalation through Template Part block attributes that could lead to remote code execution. Alongside it: an unauthenticated stored XSS through shortcode attributes in comments, a denial of service through batched XML-RPC pingbacks, a multisite route from Administrator to Super Admin, and several SQL injection and XSS fixes.

The fixes were backported to every branch back to 4.7, so even neglected sites can be patched without a major upgrade. If you look after client WordPress sites, check them today rather than trusting that automatic minor updates ran. Some hosts and older configs disable them.

None of this is a knock on WordPress. A release like this is the routine price of running the most targeted CMS on the web, and the team handled it well. But if you keep finding yourself doing this kind of firefighting, I wrote about the signs you have outgrown WordPress and, in fairness, when WordPress is still the right choice.

WordPress 7.2 RC1 also landed on 17 November, with the final release still set for 8 December. If you maintain plugins, the dev note on preparing for jQuery 4 is the one to read first.

Nuxt UI: stored XSS fixed, go to 4.12.2 or later

Nuxt UI 4.12.1 went out on 16 November as a security release for a stored XSS through the as prop in SSR markdown rendering (GHSA-x9jw-j844-v24h). 4.12.2 followed the same day to complete the fix, so 4.12.1 alone is not enough. If you render user or CMS markdown through Nuxt UI, upgrade now. 4.13.0 arrived on 18 November with Toggle and ToggleGroup components and promise toasts, if you want a reason to go straight there.

Elsewhere, Nuxt Content 3.17.0 (17 November) adds Nuxt 5 support, and DevTools 4.2.0 now warns about payload size, which I like. There has been no Nuxt core release since 4.6.4 on 2 November, so there is nothing to do there if you build with Vue and Nuxt.

Supabase: custom OIDC providers and account recovery

Since 17 November you can register any OIDC provider for third-party auth from the Dashboard by adding its issuer URL, and manage custom issuers through the Management API. If you have been bridging an identity provider that was not on the list, this removes a layer.

On 13 November Supabase also added a backup password for accounts that sign in with GitHub or another OAuth provider, plus MFA recovery codes. Set both up in Account Security. Losing access to the account that owns your production projects is not a problem you want to discover on a Friday.

One date to diary if your product runs on Supabase: the Hono, H3, Elysia and NestJS adapters in @supabase/server are removed on 1 December.

What I published

How my games run inside HD CMS closed out games week. This morning's note asks can I use AI to automate my business? and answers it for a small business. If that question is on your mind, my page on AI for business covers how I help with it. Last week's round-up is here.

If any of this lands on your desk and you would rather hand it over, get in touch.

Related reading

More on Supabase →