CVE-2026-119977 Known exploited

WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution

Products / packages WordPress Foundation WordPress

Published 31/10/2026, 05:33:07 UTC

Severity and exploitation

Known exploited

KEV checked 05/11/2026, 06:00:33 UTCAdded 2026-11-03

Wordfence · CVSS:3.1 · 8.1

Assessment vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Severity

high8.1

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Confirmed exploited · CISA KEV

CISA has recorded exploitation in the wild. Review its required action.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Source guidance available

Review the recorded instructions. Guidance may be a workaround rather than a fixed version.

What this means

WordPress Core versions 4.7.0 to 7.1.3 may be vulnerable due to predictable staging paths during upgrades. Unauthenticated attackers may exploit this weakness. The impact is uncertain.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

WordPress Foundation · Wordfence

WordPress

25 ranges

Wordfence version evidence

Check a product version

Compare with this publisher’s ranges. This does not inspect your installation.

affected

4.7.0 → through 4.7.38

semver versions

4.8.0 → through 4.8.33

semver versions

4.9.0 → through 4.9.34

semver versions

5.0.0 → through 5.0.30

semver versions

5.1.0 → through 5.1.27

semver versions

5.2.0 → through 5.2.29

semver versions

5.3.0 → through 5.3.26

semver versions

5.4.0 → through 5.4.24

semver versions

5.5.0 → through 5.5.23

semver versions

5.6.0 → through 5.6.22

semver versions

5.7.0 → through 5.7.20

semver versions

5.8.0 → through 5.8.18

semver versions

5.9.0 → through 5.9.19

semver versions

6.0.0 → through 6.0.17

semver versions

6.1.0 → through 6.1.15

semver versions

6.2.0 → through 6.2.14

semver versions

6.3.0 → through 6.3.13

semver versions

6.4.0 → through 6.4.13

semver versions

6.5.0 → through 6.5.13

semver versions

6.6.0 → through 6.6.10

semver versions

6.7.0 → through 6.7.10

semver versions

6.8.0 → through 6.8.11

semver versions

6.9.0 → through 6.9.10

semver versions

7.0.0 → through 7.0.7

semver versions

7.1.0 → through 7.1.3

semver versions

Other versions: unaffected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA required action ↗

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-accessible staging paths used during full-package core upgrades. This makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.

References

10 sources

www.wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250

Security advisoryWordfence

core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php

Source referenceWordfence

core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php

Source referenceWordfence

core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php

Source referenceWordfence

core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php

Source referenceWordfence

core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.php

Source referenceWordfence

View 4 more references

core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/update-core.php

Source referenceWordfence

wordpress.org/news/2026/10/wordpress-7-1-4/

Source referenceWordfence

www.wordfence.com/threat-intel/vulnerabilities/wordpress-core/wordpress-core-470-713-unauthenticated-upgrade-window-staged-installer-remote-code-execution

Security advisoryCISA-ADP

www.cisa.gov/known-exploited-vulnerabilities-catalog

Security advisoryCISA-ADP

Inside the record

Evidence available

Package identity · not supplied

Version evidence

Remediation guidance · not supplied

Weakness classification

Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-119977

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-367 ↗

CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition

Wordfence

Contributing organizations · 2

Wordfence

Assigning organization

2026-10-31

CISA-ADP

Additional data publisher

2026-11-04

Timeline

All times UTC

31 Oct 2026, 05:33
Advisory published
Publication date supplied by the source.
3 Nov 2026
Added to CISA KEV
CISA recorded known exploitation.
4 Nov 2026, 04:56
Source updated
Latest modification date supplied by the source.
4 Nov 2026, 05:07
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes

CVE · CVE-2026-1199772026-11-04

Observed 2026-11-04T05:07:04.484Z · upstream updated 2026-11-04T04:56:31.158Z

Prioritization updated

before

[
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-03T20:50:05.434105Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "active"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "total"
      }
    ]
  }
]

after

[
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-03T00:00:00+00:00",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "active"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "total"
      }
    ]
  }
]

CVE · CVE-2026-1199772026-11-03

Observed 2026-11-03T21:19:26.235Z · upstream updated 2026-11-03T20:58:23.478Z

References changed

before

[
  "https://www.wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250?source=cve",
  "https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php#L378",
  "https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php#L162",
  "https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php#L1549",
  "https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php#L282",
  "https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.php#L346",
  "https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/update-core.php#L1545",
  "https://wordpress.org/news/2026/10/wordpress-7-1-4/"
]

after

[
  "https://www.wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250?source=cve",
  "https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php#L378",
  "https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php#L162",
  "https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php#L1549",
  "https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php#L282",
  "https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.php#L346",
  "https://core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/update-core.php#L1545",
  "https://wordpress.org/news/2026/10/wordpress-7-1-4/",
  "https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-core/wordpress-core-470-713-unauthenticated-upgrade-window-staged-installer-remote-code-execution",
  "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-119977"
]

Prioritization updated

before

[]

after

[
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-03T20:50:05.434105Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "active"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "total"
      }
    ]
  }
]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.

Reading the signals

Severity · CVSS: Technical impact and attack conditions. The headline is the highest imported catalog score; sources may disagree.
Observed exploitation · KEV: CISA lists this vulnerability as known exploited.
Predicted exploitation · EPSS: No EPSS estimate available in this record.

CISA-ADP · SSVC

CISA Coordinator · 2026-11-03

Exploitation: active
Automatable: no
Technical Impact: total

SSVC describes the publisher’s decision context. Your organization’s exposure and priorities may differ.

Record identifiers

Aliases: None recorded

Source evidence

Request a correction or dispute

Start with the assigning organization for this record. Include the CVE ID, the disputed information, and supporting evidence. A dispute does not itself reject a record.

Find the responsible CNA →Official dispute and escalation process ↗

CVE CVE-2026-119977