Originally published on ConvertElementor .
Next.js 16.4.5 and 15.5.29 patch seven vulnerabilities, most of them in the caching layer — and several can serve one user's data to another. Here's what was fixed, who needs to patch, and the caching lessons every WordPress and Elementor site owner should take home.
The Patch I Did Not Expect to Be Writing About
I spend most of my working life inside WordPress and Elementor. Next.js is not my daily driver, and I will not pretend otherwise. But I pay attention to what happens in the wider web development world, because the same mistakes keep showing up in every stack — and this week, Next.js gave us a textbook example.
On November 3, 2026, Vercel shipped Next.js 16.4.5 and 15.5.29, fixing seven vulnerabilities — one High, six Medium — and most of them are caching bugs: under the right conditions, a cached result computed for one user, tenant, or locale could be served to somebody else entirely.
If you run a WordPress site, that should sound familiar.…