Contact us
← Article questionsWhat’s the evidence?

CVEHit Business Advisory by IntegrityLab.ai

What’s the evidence?

WordPress core update-window code execution — CVE-2026-119977: Business Triage

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

← Back to article questions

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…