Skip to main content
WordPress

WordPress fixes 18 flaws, with patches for older versions to follow

WordPress 7.1.5 fixed 18 security flaws on 18 November, four needing no login. Sites on 4.7 to 6.5, more than one in ten, got their fixes up to just over three hours after the flaws were made public.

By Published Updated
A cartoon web page covered in three sticking plasters with a warning shield on its corner, beside a small robot holding up a sign with a refresh arrow

Updated, 18 November 2026, 21:01 GMT. WordPress has now shipped the fixes for every older branch back to 4.7. The last, 4.7.40, came out at 20:21 GMT, just over three hours after WordPress published the list of flaws. We’ve updated the version table, added how many sites were on those older versions, and changed the headline.

WordPress released version 7.1.5 on 18 November and calls it a security release. Its release post lists 18 security fixes and two hardening changes, and tells site owners to update immediately.

Four of the 18 can be used by someone who isn’t logged in to the site, according to WordPress’s own labels. One is a privilege escalation through Template Part block attributes that WordPress says “could lead to remote code execution”, which could let an attacker run code on the server.

What 7.1.5 fixes

The release post describes each fix in a line. The ones that need no login are:

  • a privilege escalation through Template Part block attributes that could lead to remote code execution;
  • a stored cross-site scripting (XSS) flaw through shortcode attributes in comments, which lets someone plant script in a comment;
  • a way to knock a site over by sending batched pingbacks through XML-RPC;
  • a REST API search route that exposes private taxonomy terms.

For eight others, WordPress names the account an attacker would need, from subscriber, the lowest role, up to administrator. These include a comment-editing permissions bypass, a leak of user email addresses and several more XSS flaws. For five, including two SQL injection flaws, the release post doesn’t say whether a login is needed.

On multisite installs, one fix stops a site administrator taking over a super admin account through Customizer menu previews.

The release post gives no CVE numbers or severity scores for the 18, and doesn’t say whether any have been used in attacks. We found no reports of attacks when we searched at about 17:30 GMT on 18 November.

Which versions have the fix

WordPress says the fixes have been backported, as a courtesy, to every branch still eligible for security fixes, back to 4.7, and that “the backports are in progress and will ship as they become ready”. It also says only the most recent version of WordPress is actively supported.

They didn’t all arrive at once. WordPress.org’s download files show 7.1.5 and the fixes for 7.0 down to 6.6 dated between 16:35 and 16:48 GMT on 18 November. When we checked at 17:31 GMT, the newest builds for 6.5 down to 4.7 were still the ones from 28 October, released with 7.1.4. Their fixes followed between 19:06 and 20:21 GMT, one branch every few minutes:

Branch Fixed version Download file dated (GMT, 18 Nov)
7.1 7.1.5 16:35
7.0 7.0.9 16:37
6.9 6.9.12 16:39
6.8 6.8.13 16:42
6.7 6.7.12 16:45
6.6 6.6.12 16:48
6.5 6.5.15 19:06
6.4 6.4.15 19:10
6.3 6.3.15 19:13
6.2 6.2.16 19:18
6.1 6.1.17 19:22
6.0 6.0.19 19:25
5.9 5.9.21 19:28
5.8 5.8.20 19:30
5.7 5.7.22 19:33
5.6 5.6.24 19:36
5.5 5.5.25 19:39
5.4 5.4.26 19:43
5.3 5.3.28 19:46
5.2 5.2.31 19:55
5.1 5.1.29 20:00
5.0 5.0.32 20:05
4.9 4.9.36 20:09
4.8 4.8.35 20:14
4.7 4.7.40 20:21

The release post doesn’t list the backport version numbers. The table comes from the download-file dates, checked at 20:57 GMT.

That gap mattered to a lot of sites. WordPress published the release post listing the 18 flaws at 17:08 GMT. WordPress.org’s usage figures, which count sites that check in with WordPress.org for updates, put 11.6% of them on 4.7 to 6.5 when we checked at 21:00 GMT. That’s more than one site in ten with no fixed version to install for about two to three hours while the list of flaws was public. Another 1% are on versions older than 4.7, which get no fixes at all.

What to do

Log in to WordPress, go to Dashboard, then Updates, and check which version you’re on.

If WordPress offers 7.1.5, select Update Now. WordPress says sites with automatic background updates switched on will start the update by themselves. Check afterwards that the version number has changed.

If your site is on an older version, the fixed release for its branch is in the table above. If it’s older than 4.7, there is no fix for that version. Moving to 7.1.5 gets the fixes, but it needs PHP 7.4 or later, according to WordPress.org’s version-check service, and a jump that size can break old themes and plugins.

Take a backup and try it on a copy first if you can.

IONOS, a large UK web host, said at 17:31 GMT that it is updating sites on its managed WordPress hosting automatically. Customers who run WordPress themselves on its web hosting, VPS, cloud or dedicated servers need to update to 7.1.5, it says.

If someone else looks after your site, ask them:

Is our WordPress site on 7.1.5, or the fixed version for its branch released on 18 November? If it’s on a version older than 4.7, when can we move to one that gets security fixes? Are automatic core updates on?

What isn’t known

It isn’t known whether any of the 18 flaws has been used in attacks, which versions each flaw affects, what their CVE numbers are or how severe each one is.

Alex De Sousa is the founder of Digital Royalty, a software development company in Portsmouth that builds websites, web apps and AI tools for UK businesses.