November 5, 2026

WordPress CVE-2026-119977 exploited: what to ask your agency

CISA lists WordPress core flaw CVE-2026-119977 as exploited, due 6 November. Which versions fix it, and what to ask the agency that runs your site.

News

Tech

CVE-2026-119977 is a WordPress core remote-code-execution flaw that CISA lists as exploited, with a due date of 6 November. WordPress 7.1.4 fixes it, and older branches get backports. Find out today who runs your WordPress site, and get the version and the core-update dates in writing. A site that took a core update before it reached 7.1.4 may need checking, not just patching: CISA marks the entry "forensic triage: Yes" (check for signs of compromise).

What is CVE-2026-119977?

CISA added the flaw to its Known Exploited Vulnerabilities (KEV) catalog on 3 November. The entry describes a time-of-check to time-of-use race (CWE-367) that lets unauthenticated attackers execute code on the server "during the upgrade window". The cause is staging paths that are predictable and web-accessible during full-package core upgrades.

CISA's due date for federal agencies is 6 November, under Binding Operational Directive 26-04. Nothing legally forces your company to meet it. We'd use it as your deadline anyway, because exploitation is confirmed and the fix has been out since 28 October.

WordPress's own release post is vaguer, calling it a weakness in the upgrade process. The National Vulnerability Database (NVD) lists affected versions as 4.7 through 7.1.3, which covers almost every site you're likely to have. Wordfence, the CNA, scores it 8.1 High in the NVD record, with attack complexity rated High. CISA's own assessment in the same record says exploitation is active and not automatable. Read that as: targeted, not a worm, but real.

Which version fixes it

Update to 7.1.4 or the fixed release for your branch. WordPress's version page for 7.1.4 lists these:

BranchFixed version
7.17.1.4
7.07.0.8
6.96.9.11
6.86.8.12
6.76.7.11
6.66.6.11
6.56.5.14
6.46.4.14
6.36.3.14
6.26.2.15
6.16.1.16
6.06.0.18
5.95.9.20

WordPress's post says the fixes were backported to "all branches eligible to receive security fixes (currently through 4.7)". If you're on 5.8 or older, the fixed builds run from 5.8.19 down to 4.7.39, and WordPress's documentation and NVD agree on them. Ask the host to confirm the exact build is running. WordPress no longer ships security updates for 4.6 or older, so it has no fixed build: the site has to move to a supported release.

Does the upgrade itself trigger it?

CISA and NVD both place the exposure in full-package core upgrades. WordPress's post says sites with automatic background updates will update on their own. No primary source says auto-updates are the trigger, and none says they're safe.

Our reading, not a published finding: the window opens whenever a core upgrade runs, so a site that updated itself overnight had the same window as one an agency updated by hand.

Does patching end it?

It might not. The KEV entry's forensic triage flag means a patched site can still be a compromised one, and the entry points to BOD 26-04 for the requirements.

Take a marketing site on 7.1.3. Say its host had auto-updates on and moved it to 7.1.4 on 29 October. KEV lists the flaw on 3 November. The version check passes, yet nobody looked at the site after the update. The version number can't tell you if anything happened in that window.

Our advice is to ask a technical person to check four things:

  1. PHP files that shouldn't exist in the web root or under wp-content.
  2. Admin accounts nobody recognises.
  3. Changes to wp-config.php.
  4. The access logs for each core-update window.

No primary source publishes indicators of compromise, so there's nothing to match against. You're looking for things that don't belong. For the same flag handled on a different product, see GitLab's KEV listing and the forensic triage steps.

Who owns your WordPress site?

For most companies the engineering team doesn't. A marketing site built by an agency, hosted by a managed provider, or kept alive by a freelancer sits outside the patching routine. Three questions sort it out:

  • Who holds admin access?
  • Who applies core updates?
  • Who is paid to?

If those are three different answers, or none, you've found the risk. It's the same drill as PHP2Shell on the KEV list, which hit the same population of forgotten PHP sites. If you've already inventoried your PHP hosts, add WordPress versions to that list.

What to ask the agency or host today

Send these in writing. A written answer is evidence, and a call isn't. Our four questions:

  1. What exact WordPress version is the site running right now? Ask for a screenshot or a command output, not a recollection.
  2. What were the date and method (automatic or manual) of every core update since 1 October, or the last three if there were fewer?
  3. Is the host on a patched build? If the site runs an older branch, who confirms the fixed build for it?
  4. Did anyone check for unexpected files or accounts after the update? Ask them to send the output.

What this means for who owns the marketing site

The decision for a CTO or VP Engineering is accountability. Name one person for every web property engineering doesn't run, and get a written update window from whoever operates each one. Inside a KEV deadline, a site nobody can account for is the finding, not the version number.

Two actions follow. First, treat any site that took a core update, including the move to 7.1.4, as needing the file-and-account check, even if it now shows the fixed version. Second, check what your agency contract says about security updates. If it's silent, that's a gap to close before the next advisory. Answering the contractor security questions covers the access and offboarding evidence a buyer will ask for, which is a useful start on the same paper trail.

If nobody can answer the four questions within a day, escalate. We track exploited-vulnerability notices like this in platform and language release notes.

FAQ

Is CVE-2026-119977 exploitable without logging in?

Yes. CISA's entry and the NVD record both describe unauthenticated attackers executing code on the server during a core upgrade. The score recorded in NVD, supplied by Wordfence, is 8.1 High, with high attack complexity.

Which WordPress version fixes CVE-2026-119977?

7.1.4 on the 7.1 branch, with fixed releases down the older branches, such as 7.0.8, 6.9.11 and 5.9.20. Sites on 5.8 or older have fixed builds from 5.8.19 down to 4.7.39; ask the host to confirm the exact build is running. 4.6 and earlier have no fix.

Do I need to act if my host manages updates?

Yes, by asking. Get the running version and the dates of recent core updates in writing, and ask whether anyone checked for unexpected files or accounts afterwards. How hosts handle updates isn't published, so don't assume.

Is the 6 November deadline binding on my company?

No. It comes from BOD 26-04 and applies to US federal civilian agencies. For everyone else it's a benchmark, and we'd treat it as your own.

Sources

Share this article

Author Image

HighCircl Editorial Team

The HighCircl editorial team writes about hiring software engineers, nearshore development, and engineering team building. Our articles draw on direct experience sourcing and placing senior developers across Poland, Hungary, Slovakia, Serbia, Slovenia, Romania, and Spain — and on candid conversations with the CTOs and engineering leads who hire them.

HighCircl is a nearshore engineering network that delivers matched candidate shortlists in 72 hours. Every piece of content we publish is informed by real engagement data: actual developer rates, real hiring timelines, and what separates engineering teams that scale cleanly from those that stall.

Take Me to the Experts

Access our network of industry-leading software engineers.

Start Now