WordPress flaw exploited during the update itself (04/11/2026)
WordPress 7.1.4 has fixed, since 28 October, a remote code execution triggerable during a core upgrade. CISA flagged it as exploited on 3 November, NCSC-NL warned on 4 November. For an SME, patching is not enough: you also have to look back.
The short version
On 28 October 2026 WordPress shipped 7.1.4, a security release fixing a WordPress vulnerability that allows remote code execution, tracked as CVE-2026-119977 and present from version 4.7 through 7.1.3[1][2]. On 3 November the US CISA added it to its Known Exploited Vulnerabilities catalog, with a remediation due date of 6 November[1][4]. On 4 November the Dutch NCSC issued an alert titled "Kwetsbaarheid in WordPress Core met actief misbruik: update nu": CVSS 8.1, likelihood of exploitation assessed as low, potential damage high[3].
What makes this WordPress vulnerability different: it targets the update itself
Most website flaws close as soon as you apply the patch. This one inverts that logic. The defect is a time-of-check / time-of-use race condition (CWE-367) in the core updater: during a full-package upgrade, WordPress briefly writes files to a predictable, web-accessible staging path. An attacker with no account who reaches those files during that short interval may execute code on the server[1].
The practical consequence for an SME: "our updates are automatic" is not an answer. The upgrade window is the attack surface. A site that updated itself between 28 October and today opened that window at least once. Patching closes the door going forward; it says nothing about what may have walked through earlier.
The vector is network-based and needs neither an account nor user interaction, but attack complexity is rated high: you have to hit the right moment. That is the gap between a base score of 8.1 and the low exploitation likelihood NCSC-NL assigns[1][3]. Low is not zero: CISA's catalog only lists flaws for which real-world exploitation is documented[4].
The timeline, in six dates
| Date | Event |
|---|---|
| 28/10/2026 | WordPress 7.1.4 security release; the release notes list thirteen security items[2] |
| 31/10/2026 | CVE-2026-119977 record published on the NVD[1] |
| 03/11/2026 | Added to CISA's Known Exploited Vulnerabilities catalog[1][4] |
| 04/11/2026 | NCSC-NL alert: update now[3] |
| 06/11/2026 | CISA remediation due date (BOD 26-04)[1] |
| 10/11/2026 | Thirteen days since the patch was published |
That timeline matters because the strictest public benchmark, CISA's, is already four days past. It legally binds only US federal agencies, but insurers and enterprise buyers use it as a yardstick. If a client asks where you stand, that is the date in their head.
Older branches: the patch may not have reached you yet
This is the least reported and most useful detail. WordPress says the security fixes were backported to every branch still eligible, back to 4.7 — but adds that those backports "are in progress and will ship as they become ready"[2]. Depending on when you read this, a site left on an older branch may still have no patch available. The only way to know is to read the exact installed version number, not the "automatic updates enabled" checkbox.
Second trap: WordPress automatic updates cover, by default, only maintenance releases of the branch you are on. A site frozen on 5.x or 6.x by a bespoke theme or an abandoned plugin will not receive 7.1.4. The next major release, 7.2, is announced for 8 December[2], which is the realistic planning window for an upgrade.
Then the scale. WordPress runs 39.3% of all websites and 58.1% of those whose content management system is known, measured on 10 November 2026[5]. For an SME in the Netherlands, Belgium, France or Luxembourg, the question is therefore not "are we affected" but "which of our sites, on which version". The forgotten brochure site, a subsidiary's blog, the old site kept "just in case" — those are the ones that hurt.
If you find an intrusion: who to notify in each of the four countries
Code execution on the server hosting your website can expose the database, and with it personal data: contact forms, customer accounts, orders. Article 33 GDPR then requires notifying the supervisory authority within 72 hours of becoming aware, unless the breach is unlikely to result in a risk to individuals. The competent authority depends on where you are established:
- Netherlands: Autoriteit Persoonsgegevens. The national CSIRT is NCSC-NL, which issued the 4 November alert[3].
- Belgium: Data Protection Authority (APD/GBA). On the cyber side, the Centre for Cybersecurity Belgium (CCB).
- France: CNIL. On the cyber side, ANSSI and its CERT-FR.
- Luxembourg: CNPD. On the cyber side, the ILR.
If your entity also falls under NIS2, an incident reporting duty sits on top of the GDPR notification, with its own deadlines and its own counterpart. The two regimes are separate and do not replace one another. To check whether you are in scope, our country pages set out the transposition sector by sector, for instance for Belgium. We do not give legal advice: these pointers refer to the texts and the authorities, and your own counsel decides your case.
What to do this week
- List your WordPress sites, including the ones nobody uses any more. An inventory with no exceptions, naming the provider responsible for each.
- Read the exact version number of each one (Dashboard, then Updates). You are looking for 7.1.4 or later on the 7.1 branch, or the maintenance release of your own branch.
- Update whatever is behind, starting with sites reachable from the internet without restriction.
- Hunt for signs of intrusion over the 28 October to today period, rather than only patching: PHP files created or modified inside core directories, new administrator accounts, unknown scheduled tasks, repeated requests to update paths in the server logs.
- Get it in writing from your provider: version installed, date updated, and the result of the intrusion check. An "it's up to date" over the phone is worth nothing in six months.
- For sites stuck on an old branch, set the upgrade date now, aiming at the 7.2 release on 8 December[2].
At CyberNovaLabs.io
This WordPress vulnerability joins a series we track week by week: the Symfony and Laravel advisories published on the same day and the PHP products NCSC-NL still lists as vulnerable tell the same story: the real risk to an SME website sits in the delay between a patch being published and being applied. Our cybersecurity for SMEs page collects the regulatory deadlines and the checks that take an hour. If you want us to look at your estate of sites and hand you the list of versions and gaps, get in touch: you get a written assessment, quoted per project.
Sources
- NVD — CVE-2026-119977 (NIST), publie le 31/10/2026, revu le 04/11/2026
- WordPress.org — WordPress 7.1.4, note de version de securite du 28/10/2026
- NCSC-NL — Kwetsbaarheid in WordPress Core met actief misbruik: update nu (04/11/2026)
- CISA — Known Exploited Vulnerabilities Catalog, ajout du 03/11/2026 (BOD 26-04)
- W3Techs — Usage statistics of WordPress (releve du 10/11/2026)
Qualified meetings, no lock-in.
Criteria in writing before launch, pay per meeting or monthly, stop with a simple email.
Read next
NGINX: five critical flaws patched urgently (18/11/2026)
Five critical flaws in NGINX, the software receiving traffic for more than 225 million websites, were fixed on 18 November 2026. Four authorities warned the same day. Your site can be exposed without having a single defect of its own.
Read the article →November 20, 2026 · 8 min readNIS2 Luxembourg: are estate agencies and syndics in scope?
Real estate appears in neither Annex I nor Annex II of the Luxembourg Act of 5 May 2026. But your supervisory authority already exists: the AED, on money laundering. Position as of 20 November 2026.
Read the article →November 10, 2026 · 7 min readAI email assistant: consent, audit trail, confidentiality
An assistant that reads and writes your email touches everything: client contracts, employee files, competitor quotes. Three things must be written down before go-live - the approval rule, the audit log, the confidentiality perimeter. Here is the specification, clause by clause, and the four regulators to know.
Read the article →November 10, 2026 · 9 min readNIS2 Netherlands: are accounting firms and fiduciaries in scope?
The Dutch law implementing NIS2 took effect on 15 August 2026. It does not name accountancy. Even so, a Dutch accounting firm or fiduciary inherits duties through three doors: the GDPR, the Wwft, and the contracts of clients who are themselves in scope. Here is what applies, and what does not.
Read the article →November 9, 2026 · 7 min readCSBN 2026: AI speeds up the cyber threat on SMEs (06/11/2026)
On 6 November 2026 the Dutch NCSC and the NCTV published their annual cyber threat assessment. Two findings matter directly to an SME: AI is already used in every phase of an attack, and the gap between a flaw being published and being exploited is now measured in hours. Here is what changes for you, country by country.
Read the article →November 9, 2026 · 6 min readNIS2 France: are manufacturers and producers in scope?
Two answers, and neither is yes. The French law does not exist yet, and manufacturing as a whole is not a NIS2 sector. What actually binds you sits elsewhere: the supply chain, customer questionnaires and the Cyber Resilience Act.
Read the article →