Contact us
← CVEHit Business AdvisoryWordPress core update-window code execution — CVE-2026-119977: Business Triage

CVEHit Business Advisory by IntegrityLab.ai

Published

WordPress core update-window code execution — CVE-2026-119977: Business Triage8.1/10High · CVSS 3.1WordfenceFix available7.1.4 or branch backportCISA assessmentCVE.org sourceKEV listingAdded Nov 3, 2026

Confirm every WordPress site runs the patched release for its version group. Research: primary sources retrieved November 11, 2026.

Check these three things.

Answer these for every WordPress site you run or pay a host to run.

  1. Confirm each site runs the patched release for its version group.
    How version groups and fixes work
    • WordPress versions belong to version groups named by their first two numbers. For example, 7.0.7 is in the 7.0 group.
    • Each group from 4.7 through 7.1 has its own affected range and its own patched release.
    • The broad wording “4.7.0 through 7.1.3” does not mean every version in between is affected. For example, 7.0.8 is patched.
    • An affected version needs its patched release even when no update is running.
    • Versions before 4.7 are not listed as affected. WordPress says only its most recent version is actively supported.
    • The version-to-fix table is under “Advisory details and fix guidance”.
  2. Find any update of the WordPress software itself that ran while a site was on an affected version.
    When the risk window opens
    • An update of WordPress itself is called a core update. It is separate from plugin or theme updates.
    • This flaw concerns core updates that use the complete WordPress package. These are called full-package core updates.
    • The opportunity exists only while both of these apply:
      • An affected installation is running a full-package core update.
      • Its temporary update files are reachable from the web.
    • Running code on the server also requires the attacker to win a brief race against WordPress unpacking those files.
    • The attacker does not need to sign in.
    • Exposure means the opportunity existed. It does not mean an attack succeeded.
    • A public WordPress login page alone proves none of these conditions.
    • Records that can show earlier exposure:
      • Date and time of each core update.
      • Version before each update.
      • Version after each update.
      • Whether the update used the complete package.
      • Whether the host serves the WordPress upgrade folder from the web.
    • Earlier exposure matters because it tells the security lead which dates to review first.
  3. Look for signs of a break-in on any site that ran an affected version.
    What the records can show
    • Records worth reviewing, especially around update dates:
      • Alerts from the host.
      • Alerts from security tools.
      • Unexpected new or changed files in the WordPress installation.
      • Unexpected administrator accounts.
      • Unexpected setting changes.
      • Web server request records.
    • Limits of these records:
      • Suspicious changes justify investigation. They do not by themselves prove this flaw was used.
      • A missing record leaves open only the conclusions the remaining evidence cannot support. For example, a missing update log can leave earlier exposure unresolved.
      • A missing record does not undo a confirmed fix.
      • A missing record does not undo other credible evidence of a break-in.
      • Finding nothing suspicious does not prove the site is safe.
    • If the records show a break-in, start incident response now. Do not wait to reconstruct the update conditions.

If a site runs an affected version, install the patched release for its group now. If records show a break-in, start incident response now, whatever its cause.

Do Now

  • Web administrator: list every WordPress site and its installed version.
    What to record
    • Site address.
    • Installed version.
    • Source of that version.
    • Date checked.
  • Web administrator: install the patched release for each affected site’s version group.
    Which release to install
    • Sites in the 7.1 group: install 7.1.4.
    • Sites in an older group: install that group’s patched release, such as 7.0.8 for the 7.0 group.
    • Alternatively, move an older site to 7.1.4. This is not required to fix this flaw.
    • If a host manages the site, ask the host to install the release.
    • Use your normal approved change process.
    • A completed update closes this flaw’s update window. It does not remove a break-in that already happened.
  • Security lead: review affected sites for signs of a break-in.
    How to handle findings
    • Send credible signs of a break-in to the incident-response owner today.
    • Do not wait to prove this flaw was the cause.
    • CISA lists this flaw as exploited. That listing does not show your sites were attacked.

Do Next

  • Web administrator: record each site’s fix status with evidence.
    Evidence to keep
    • Installed version after the update.
    • Date the update completed.
    • Source of that record.
    • Date checked.
  • Web administrator: list updates of the WordPress software that ran on affected versions.
    Why the dates matter
    • Collect the update records listed in the second check.
    • Ask the host for any of those records it holds.
    • Give the dates to the security lead to focus the break-in review.
    • Do not delay incident response while these records are gathered.
  • Business owner: confirm the work is complete for each affected site.
    What counts as done
    • Records show the patched release on each affected site.
    • A site that cannot be patched yet has a dated plan and an owner.
    • Each affected site has a recorded break-in review result.
    • Each open question is marked Unknown and has an owner.
    • The compliance owner has checked whether any contract or regulation sets a deadline for KEV-listed flaws.

Check your own records.

  • Use your approved AI tool.
  • Require evidence. Flag unknowns.

Read the prompt

The reported finding

Race condition during full-package core updates

Original advisory →
Required conditions
  • WordPress advisory: during a core update that uses a complete package, new files were extracted to a predictable folder inside the web-served upgrade folder.
  • CVE record: predictable, web-accessible staging paths used during full-package core upgrades.
  • Both sources say the attacker does not need to sign in.
Reported outcome
  • An attacker who wins the race could execute code on the server.
  • Both sources tie this outcome to the update window.
Ratings
  • Wordfence is the CVE Numbering Authority (CNA), the organization that assigned this CVE. It gives a CVSS 3.1 score of 8.1, High.
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
  • Attack Complexity High means success depends on conditions outside the attacker’s control. The WordPress advisory, not the score, says the opportunity exists only during an update.
  • WordPress rates the flaw Low. The sources do not explain the difference.
  • Neither rating shows the impact on your company.
Known exploitation
  • CISA assessment on the CVE.org record, dated November 3, 2026:
    • Exploitation active: CISA recorded evidence that the flaw has been exploited.
    • Automatable no: CISA judged the attack cannot be reliably automated from start to finish. This does not measure how often attacks happen.
    • Technical Impact total: a successful attack could give the attacker full control of the affected software.
  • CISA added the flaw to its Known Exploited Vulnerabilities (KEV) catalog on November 3, 2026. Known ransomware use: Unknown.
  • The KEV listing does not show your company was attacked.
  • The KEV listing does not say how often attacks occur.
  • The KEV entry set a November 6, 2026 federal due date under CISA directive BOD 26-04. That date has passed. This advisory has not checked whether it applies to you. The flaw remains relevant after that date.
Source chronology
  • October 28, 2026: WordPress released 7.1.4 with this fix. The CVE record lists the same date for disclosure.
  • October 29, 2026: WordPress published advisory GHSA-4w3m-c66w-69mg. The copy retrieved November 11, 2026 shows “No known CVE”.
  • October 31, 2026: Wordfence published CVE-2026-119977.
  • November 3, 2026: CISA’s assessment on the CVE record is dated this day.
  • November 3, 2026: CISA added the flaw to the KEV catalog.
  • The WordPress advisory does not name the CVE. This brief treats them as one flaw because the CVE record:
    • Cites the WordPress 7.1.4 release post.
    • Credits the same finder.
    • Lists the same affected ranges.

Fix guidance

  • Fix available: WordPress 7.1.4, with the fix backported to every group back to 4.7.
  • Upgrade options for an affected site:
    • The patched release for its version group.
    • WordPress 7.1.4.
  • Moving every site to 7.1.4 is not required for this flaw.
  • A completed patched update closes this flaw’s update window. It does not rule out a break-in during an earlier update.
  • The October 28 release post said backports were in progress. The advisory, published October 29, lists a patched release for each group. Confirm the installed release from your records.
Version groupAffected versionsPatched release
7.17.1.0–7.1.37.1.4
7.07.0.0–7.0.77.0.8
6.96.9.0–6.9.106.9.11
6.86.8.0–6.8.116.8.12
6.76.7.0–6.7.106.7.11
6.66.6.0–6.6.106.6.11
6.56.5.0–6.5.136.5.14
6.46.4.0–6.4.136.4.14
6.36.3.0–6.3.136.3.14
6.26.2.0–6.2.146.2.15
6.16.1.0–6.1.156.1.16
6.06.0.0–6.0.176.0.18
5.95.9.0–5.9.195.9.20
5.85.8.0–5.8.185.8.19
5.75.7.0–5.7.205.7.21
5.65.6.0–5.6.225.6.23
5.55.5.0–5.5.235.5.24
5.45.4.0–5.4.245.4.25
5.35.3.0–5.3.265.3.27
5.25.2.0–5.2.295.2.30
5.15.1.0–5.1.275.1.28
5.05.0.0–5.0.305.0.31
4.94.9.0–4.9.344.9.35
4.84.8.0–4.8.334.8.34
4.74.7.0–4.7.384.7.39

What IntegrityLab.ai can check

  • IntegrityLab can report a reachable WordPress login page.
  • That observation does not establish:
    • The installed version.
    • This CVE.
    • An active update window.
    • Compromise.
  • The administrator or host must establish these from authorized records:
    • The installed version.
    • Update completion.

How to read the score

Wordfence CVSS 3.1: 8.1 (High). WordPress: Low. Use the conditions and update history alongside the score to set your priorities.

Sources and vendor guidance

Need an independent review of your public exposure?

See IntegrityLab.ai →

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…