WordPress fixed 17 security issues on October 28. Three weeks later, the WordPress 7.1.5 security release fixed 20 more, and WordPress says to update immediately.
That release came out on November 18. If your site runs on WordPress, someone has to install it. Find out today who that is.
What the WordPress 7.1.5 security release fixed
WordPress listed 20 security fixes in the 7.1.5 release post. The worst, in its own words, is a privilege escalation through Template Part block attributes "that could lead to remote code execution." That means a stranger's code running on your server.
Patchstack, a WordPress security company, went through the list the same day. Its security research lead, Dave Jong, counted 18 real vulnerabilities and two hardening changes.
Most of the 18 let someone plant a script on a page or read what they should not see, like commenter emails and IP addresses.
One sits in the Comment Date block, the line that prints the date under a comment. Per Patchstack, a script planted there needs no click. It runs for every visitor who loads the page.
Two security releases in three weeks
The release before this one, 7.1.4, came out on October 28 with 17 fixes, Patchstack notes. One was a flaw in how WordPress updates itself, and attackers went after it within days.
On November 3 the US Cybersecurity and Infrastructure Security Agency added that flaw to its list of flaws under active attack. We wrote it up as the WordPress update flaw.
Neither WordPress nor Patchstack says any of the new 20 has been used in an attack yet. No CVE numbers, the IDs security tools track flaws by, had been assigned when Patchstack published. The details are public all the same.
Release notes tell site owners what to fix. They tell everyone else where to look.
Who installs it on your site
WordPress says a site with automatic background updates starts the update on its own. Whether yours has them on was decided by whoever set the site up. If you do not know who that was, that is the first thing to find out.
The fixes go back to every version from 4.7 up. A site still on 4.6 or older gets none of them, Patchstack says.
Patchstack's other advice is about people. Six of the fixes concern what Contributor accounts and higher can reach, so it says to check who holds one.
Take a flower shop in Pottsville. The site runs on WordPress, and a part-timer has a Contributor login to post the Friday specials. That one login is the kind of account those six fixes are about.
What to ask whoever runs your site this week
For most small businesses the host or a web person runs the updates. Send them these in writing:
- Is the site on WordPress 7.1.5, or the patched release for its older version?
- Are automatic background updates on, and who hears about it when one runs?
- Which accounts hold Contributor or higher, and does each still belong to someone who works here?
- Is the site on 4.6 or older, which gets no security fixes at all?
If they find an account nobody recognizes, have them keep the logs before deleting anything. Then change the website and hosting passwords.
A plain-page site has nothing on this list to patch
Freeborn Digital builds every website as plain pages: HTML, CSS and JavaScript, the three things a browser reads. There is no WordPress, no PHP, no plugin and no database on the site.
The Template Part block, the Comment Date block, the comment system and the Contributor role are all parts of WordPress. A Freeborn Digital site has none of them, so the 20 fixes have nothing to land on.
Back at the flower shop, the Friday specials still go up each week. The owner texts them to Freeborn Digital and they are on the site that day. There is no Contributor login on the pages to audit.
Freeborn Digital builds this as custom websites, launches the site and keeps it current.
Questions about the WordPress 7.1.5 security release
Is WordPress 7.1.5 being attacked?
Neither WordPress nor Patchstack has said so. The update flaw fixed in 7.1.4 came under attack within days of its fix, so the time to update is before anything is reported.
Will my WordPress site update to 7.1.5 by itself?
If automatic background updates are on, WordPress says the update starts on its own. Ask your host whether they are on, and whether the site actually reached 7.1.5.
My site is on an older WordPress version. Is it covered?
WordPress sent the fixes back to every version from 4.7 up. A site on 4.6 or older gets no security fixes and needs a full upgrade.
Does a Freeborn Digital website need this update?
No. A Freeborn Digital website has no WordPress on it. The pages are plain HTML, CSS and JavaScript on your own domain, so there is no 7.1.5 to install.
WordPress counted 17 fixes in October and 20 in November. If your site runs on it, send the four questions today.
For a site with nothing to count, tell Freeborn Digital what the business does. A few lines at freeborndigital.com/start is enough, or text 570-617-7655.
Want this for your business?
Start a Project