Contact us
← Article questionsDoes this affect us?

CVEHit Business Advisory by IntegrityLab.ai

Does this affect us?

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

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.

← 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…