← back to feed
CVE-2026-119977

CVE-2026-119977

waiting for further signalsZero needs more public information before it can validate it.

GHSA-p6jj-qrp3-7m4g ↗EUVD-2026-114575 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.−1d
WordPress Foundation WordPress >= 4.7.0, <= 4.7.38; >= 4.8.0, <= 4.8.33; >= 4.9.0, <= 4.9.34; >= 5.0.0, <= 5.0.30; >= 5.1.0, <= 5.1.27; >= 5.2.0, <= 5.2.29; >= 5.3.0, <= 5.3.26; >= 5.4.0, <= 5.4.24; >= 5.5.0, <= 5.5.23; >= 5.6.0, <= 5.6.22; >= 5.7.0, <= 5.7.20; >= 5.8.0, <= 5.8.18; >= 5.9.0, <= 5.9.19; >= 6.0.0, <= 6.0.17; >= 6.1.0, <= 6.1.15; >= 6.2.0, <= 6.2.14; >= 6.3.0, <= 6.3.13; >= 6.4.0, <= 6.4.13; >= 6.5.0, <= 6.5.13; >= 6.6.0, <= 6.6.10; >= 6.7.0, <= 6.7.10; >= 6.8.0, <= 6.8.11; >= 6.9.0, <= 6.9.10; >= 7.0.0, <= 7.0.7; >= 7.1.0, <= 7.1.3
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
ETK-2026-3145Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss8.1cna vendorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
34msince last run
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
kev−24htrigger signal (cve.org) +0hwaiting for further signals+3h26m
−18h
−12h
−6h
0

description

WordPress Core versions 4.7 through 7.1.3 are affected by an upgrade staging-path race condition. An unauthenticated attacker may execute code on the server during a full-package core upgrade if the temporary staging paths are publicly accessible.

mitigation

Prevent public access to temporary upgrade and staging directories, and avoid full-package core upgrades on internet-facing hosts until remediation guidance is available. Perform necessary upgrades in a controlled maintenance window.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-31 05:33Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
−1d

outcome

No artifact: no remotely reachable path found.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-30 00:00Z
  2. 2026-10-31 05:33Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-119977

this entry in the feed

GET /api/v1/feed/CVE-2026-119977

{
  "etk_id": "ETK-2026-3145",
  "cve_id": "CVE-2026-119977",
  "display_id": "CVE-2026-119977",
  "ghsa_id": "GHSA-p6jj-qrp3-7m4g",
  "euvd_id": "EUVD-2026-114575",
  "status": "rejected_out_of_scope",
  "anchor_state": "anchored",
  "title": "Race condition in WordPress Core upgrade staging paths",
  "summary": "WordPress Core versions 4.7 through 7.1.3 are affected by an upgrade staging-path race condition. An unauthenticated attacker may execute code on the server during a full-package core upgrade if the temporary staging paths are publicly accessible.",
  "mitigation": "Prevent public access to temporary upgrade and staging directories, and avoid full-package core upgrades on internet-facing hosts until remediation guidance is available. Perform necessary upgrades in a controlled maintenance window.",
  "vendor": "WordPress Foundation",
  "product": "WordPress",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.7.0, <= 4.7.38",
        ">= 4.8.0, <= 4.8.33",
        ">= 4.9.0, <= 4.9.34",
        ">= 5.0.0, <= 5.0.30",
        ">= 5.1.0, <= 5.1.27",
        ">= 5.2.0, <= 5.2.29",
        ">= 5.3.0, <= 5.3.26",
        ">= 5.4.0, <= 5.4.24",
        ">= 5.5.0, <= 5.5.23",
        ">= 5.6.0, <= 5.6.22",
        ">= 5.7.0, <= 5.7.20",
        ">= 5.8.0, <= 5.8.18",
        ">= 5.9.0, <= 5.9.19",
        ">= 6.0.0, <= 6.0.17",
        ">= 6.1.0, <= 6.1.15",
        ">= 6.2.0, <= 6.2.14",
        ">= 6.3.0, <= 6.3.13",
        ">= 6.4.0, <= 6.4.13",
        ">= 6.5.0, <= 6.5.13",
        ">= 6.6.0, <= 6.6.10",
        ">= 6.7.0, <= 6.7.10",
        ">= 6.8.0, <= 6.8.11",
        ">= 6.9.0, <= 6.9.10",
        ">= 7.0.0, <= 7.0.7",
        ">= 7.1.0, <= 7.1.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WordPress",
      "purl": null
    }
  ],
  "cwes": [
    367
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 0.00289055,
  "t0_at": "2026-10-31T05:33:07.059000+00:00",
  "signals": {
    "kev": {
      "at": "2026-10-30T00:00:00+00:00",
      "days": -1,
      "is_lower_bound": false,
      "measured_at": "2026-10-31T05:33:07.059000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-119977"
    },
    "trigger_signal": {
      "at": "2026-10-31T05:33:07.059000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-31T05:33:07.059000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-119977"
    }
  }
}

published 2026-10-31 05:59Z
last change 2026-10-31 09:10Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.