WordPress Core Update Race: When the Update Becomes the Attack Path
Note: There were 63,000 attempts to exploit this vulnerability within 24 hours after the patch was released on Oct 28, 2026.
The core-update race fixed in WordPress 7.1.4 could lead to unauthenticated remote code execution. Xint also identified the issue independently before disclosure and validated both the exploit path during a real update and the 7.1.4 fix. This post explains the root cause, which current and future update paths require attention, and how to update safely.
TL;DR
Before the fix, WordPress extracted a core-update ZIP into a predictable directory below
wp-content/upgrade/. An attacker could submit their own database settings tosetup-config.php, create a newwp-config.phpthere, and have the updater copy it into the live site, causing the victim's WordPress installation to use the attacker database.Xint independently discovered a race in the WordPress core update process that leads to unauthenticated remote code execution, and WordPress fixed the root cause in 7.1.4 and the maintenance-branch security releases published with it. The official WordPress 7.1.4 security credit belongs to Umut Bayram of Picus, who reported the issue independently.
Sites that completed the automatic security update to one of the fixed branch releases remain protected in later upgrades, including upgrades that use a complete ZIP. WordPress 7.0.8 and the fixed maintenance-branch releases listed in section 5.1 carry the same fix as 7.1.4.
The immediate concern is an operator about to click Update Now on an unpatched release. An update from unpatched WordPress 2.7 through 7.0.7—including pre-fix releases in every 3.x through 6.x branch—to 7.1.4 uses a ZIP containing the files required to trigger the vulnerability. A clean 7.1–7.1.3 installation currently receives a partial without that file when moving to 7.1.4, but it can face the same attack if a later update becomes available before 7.1.4 is installed.
Item | Details |
|---|---|
Impact | Unauthenticated PHP code execution during a core update |
Vulnerable updater | Unpatched WordPress releases from 2.7 through 7.1.3 |
Releases that fix this vulnerability | 7.1.4 and the security releases for every eligible branch from 7.0 through 4.7 (full list) |
Immediate concern in the current 7.1.4 transition | Unpatched WordPress 2.7 through 7.0.7, including pre-fix releases in every 3.x–6.x branch |
Future-transition concern | Sites that remain on 7.1–7.1.3 until an update after 7.1.4 becomes available |
🔧 Immediate action
If the site already runs a fixed release, verify its core checksums. Before clicking Update Now, apply the pre-update hotfix in section 5.2 when updating an unpatched release from WordPress 2.7 through 7.0.7, applying a new update after 7.1.4 while still running 7.1–7.1.3, or whenever the selected ZIP is uncertain.
1. Why We Looked at the Update Process
Nearly every site eventually runs the update process, which can download files as the web-server account and replace the live core. Security review usually focuses on the code inside the new release. Xint instead traced the temporary program the server becomes during the few seconds in which that code is installed. This exposed a point where a legitimate official ZIP briefly became a second WordPress instance capable of handling external requests.
2. How a Normal Core Update Works
2.1 The update process
For automatic updates, WordPress periodically checks for new releases and applies those allowed by the site's settings. A manual update begins immediately when an administrator clicks the core-update button under Dashboard → Updates. Only the starting point differs; the installation process is the same.
Select an update ZIP for the installed version and current file state.
Download the official ZIP from WordPress.org.
The currently installed WordPress version extracts it below
wp-content/upgrade/.Check the downloaded files and load the new
wp-admin/includes/update-core.php.Copy the extracted files from the temporary directory into the live WordPress directory and perform any required database update.
Delete the temporary directory and leave maintenance mode.
2.2 How WordPress chooses partial, no-content, or full
A partial ZIP contains only files changed between two releases. no-content contains the complete core without bundled content, full contains the full distribution, and new-bundled also adds newly bundled content to an older installation.
WordPress.org returns several update ZIP candidates, and the updater installed on the server chooses one in this order:
It uses a
partialwhen one exists for the exact installed release, the operation is not a reinstall, and the installed core files match the official copies from WordPress.org.Otherwise it selects
new-bundledwhen that transition requires bundled content, thenno-contentwhen available, and finallyfull.full,no-content, andnew-bundledcontainwp-admin/setup-config.php. A partial contains it only when that file itself changed between the two releases.
The selected ZIP is therefore not determined by the destination version alone. The source release, matching partial, reinstall state, and pre-update checksum result all matter. The absence of setup-config.php from one current partial does not mean the source updater has been fixed. If the site remains unpatched until a later release, the API offer and package contents may change while the first extraction is still performed by the old updater.
3. The Bug: A Short Attack Window During a Normal Update
3.1 How steps 3 and 5 created the race
Through WordPress 7.1.3, three update behaviors met at the same point:
The temporary-directory name was derived directly from the public update ZIP filename, so anyone could calculate its exact URL.
WordPress created that directory below
wp-content/upgrade/, within the web root of the official Apache distribution. PHP files extracted there could be opened and executed through the web just like the live site.WordPress did not keep a fixed list of files from the original ZIP. It read the temporary directory again while copying, so a file created there by an external request could be copied into the live site.
Our audit of every official stable tag found this structure from WordPress 2.7, which introduced the built-in core update feature, through 7.1.3. Throughout that range, the default WP_CONTENT_DIR was wp-content below the WordPress web root, and WordPress neither shipped nor created a file that denied HTTP access or PHP execution below upgrade/. A standard Apache/PHP deployment therefore executed the extracted PHP files when their direct URLs were requested. Releases through 2.6.5 do not have this update path. The fixed maintenance releases published on 2026-10-28 and WordPress 7.1.4 give every temporary directory a random name.
3.2 From setup-config.php to remote code execution
wp-admin/setup-config.php accepts database settings without authentication during a new WordPress installation. When opened from the temporary update directory, it does not find the live site's existing wp-config.php, so it can create a new configuration file inside that temporary copy.
The exploit proceeds as follows:
From the public update ZIP name, the attacker calculates the exact URL of
setup-config.phpinside the temporary directory and repeatedly sends database settings to it.Once the update extracts the file, one request succeeds. A PHP process on the victim server connects to the attacker's database and creates a new
wp-config.phpin the temporary directory.Before the fix, the updater read the temporary directory immediately before copying it. The attacker-created
wp-config.phpentered that file list and replaced the live configuration.After the update, the victim's live WordPress site began using the attacker database. The attacker signed in to the victim site with an administrator account prepared in that database.
The attacker then used WordPress's normal plugin upload feature to upload and execute PHP with the victim web server's privileges.
The PoC Xint submitted through a vulnerability reporting platform used the official update from WordPress 7.0.4 to the official 7.1.3 no-content ZIP. In both automatic and manual updates, the temporary wp-config.php replaced the live configuration. The completed site ran WordPress 7.1.3 with its live DB_HOST pointing to the attacker database. An administrator account in that database authenticated at the victim's /wp-admin/, uploaded a plugin, and executed PHP as www-data.
The attacker database was therefore not limited to the temporary WordPress copy. In the original vulnerable flow, the live wp-config.php was replaced, and the victim site continued using the attacker database until an operator restored its configuration.
The attacker can begin sending requests when the update is announced. The file exists for seconds, but repeated requests can wait days for an administrator to click Update Now and still land inside that interval. The attack requires no victim account, victim database credential, SSH access, WordPress.org compromise, or MITM position.
3.3 Exposure in the current 7.1.4 transition and later updates
We checked the official en_US offers and actual archives as of 2026-10-29.
Manual update from unpatched WordPress 2.7 through 7.0.7 to 7.1.4: This includes pre-fix releases in every 3.x through 6.x branch. There is no matching partial. Depending on the source release, the update selects
full,new-bundled, orno-content, all of which containsetup-config.php. WordPress 7.1.4 prevents the temporarywp-config.phpfrom replacing the live configuration, but the first extraction still uses the old code, so PHP can still be executed through the temporary WordPress copy.Normal update from 7.1 through 7.1.3 to 7.1.4: When the installed core files are unchanged from the official copies, WordPress selects a matching partial, and none of the four current partials contains
setup-config.php. The attack does not start on this default path, but the installed updater itself remains unpatched.Automatic security update within a maintenance branch: The matching partial leading to the fixed release does not contain
setup-config.php. Once that update completes, subsequent updates use temporary directories with random names.
The decisive factor for later upgrades is not whether a future offer uses a partial or complete ZIP. It is whether the currently installed updater that extracts that ZIP is fixed. WordPress 7.0.8 is not an older vulnerable counterpart to 7.1.4; it is the maintenance release that backports the same security fix to the 7.0 branch. A site that has completed the move to 7.0.8 therefore remains protected when it later upgrades to a release such as 7.2, even if that upgrade uses a complete ZIP. A site still running 7.0.7 or earlier performs its first extraction with the old predictable-directory code and is exposed whenever that selected ZIP contains setup-config.php.
Here, WordPress 2.7 through 7.0.7 is the unpatched package range confirmed for the current 7.1.4 offer, not the full boundary of vulnerable updater code. Releases 7.1 through 7.1.3 continue to create predictable temporary directories until 7.1.4 is actually installed. Their current matching partials omit setup-config.php, but a first update to a release after 7.1.4 may have no matching partial, may include the file because it changed, or may select full, no-content, or new-bundled.
Any of these package choices exposes a predictable temporary WordPress copy again. A later release's update-core.php prevents the temporary wp-config.php from replacing the live configuration, but an attacker can execute PHP through that temporary copy and write into the live WordPress directory. The current 7.1–7.1.3 partial path is safe only because those ZIPs omit setup-config.php, not because the updater installed on the server has been fixed. Do not infer the current state from the automatic-update setting alone; a site restored from an old backup or one whose update failed still needs an installed-version check.
3.4 How 7.1.4 fixes the root cause
The public WordPress 7.1.4 changes add three defenses:
Add 16 random characters to every temporary update-directory name.
Create
wp-content/upgrade/index.phpfirst so a directory listing does not reveal the random name.Do not copy a newly created
wp-config.phpfrom the temporary directory into the live site.
This directly fixes the root cause. After 7.1.4 or the corresponding security release for an older branch is installed, an attacker cannot calculate the temporary-directory URL in advance. Later upgrades remain protected even when they use a complete ZIP, because the fixed updater creates the random directory before extraction.
4. The First Update to a Fixed Release Is Still an Attack Surface
The release of a fix does not make it safe to immediately click Update Now on an unpatched site.
Downloading a ZIP that contains the fix is not the same as extracting that ZIP with fixed updater code.
When an operator clicks Update Now on an unpatched site to install WordPress 7.1.4, the update proceeds as follows:
The old
class-wp-upgrader.phpalready installed on the server downloads the 7.1.4 ZIP and extracts it under a predictable temporary-directory name. The random-directory fix inside the ZIP has not been installed yet, so it cannot protect this first extraction.If one of the attacker's repeated requests reaches
setup-config.phpat this point, it creates a temporary WordPress copy that uses the attacker database.Before copying the remaining files, WordPress loads the new
update-core.phpfrom the 7.1.4 ZIP. This code refuses to copy the temporarywp-config.phpinto the live site, preventing the original technique from replacing the live database configuration.The temporary WordPress copy is nevertheless already running and reachable. Before cleanup removes it, the attacker can sign in with an administrator account prepared in the attacker database, execute PHP, and use the web server's privileges to leave a file in the live WordPress directory.
Only after installation completes does the new
class-wp-upgrader.phpremain on the server. Subsequent updates then use random temporary-directory names.
Our validation showed the distinction directly:
7.0.4 → 7.1.3: The pre-fix
update-core.phpcopied the temporarywp-config.phpinto the live site, causing the live WordPress installation to use the attacker database.7.0.4 → 7.1.4: The new
update-core.phpblocked that configuration copy, so the live database settings remained intact. The attacker could still authenticate to the temporary WordPress copy, execute PHP, and write a file into the live WordPress directory.
The first update from an unpatched release to a fixed release must therefore be protected before it starts. Once 7.1.4 or the corresponding fixed maintenance release is installed, later updates are protected. Until then, apply the pre-update hotfix in section 5.2 before clicking Update Now.
5. Response
5.1 Check the installed version
When server access is available, use WP-CLI, the WordPress command-line tool, to check the installed version:
wp core version --path=/var/www/htmlReleases that fix this vulnerability
As of 2026-10-29, the following official releases contain this fix. We confirmed all three defenses in each of these 25 tags: a random temporary-directory name, an index.php that prevents listing the upgrade/ directory, and exclusion of a temporary wp-config.php from the live-site copy.
Branch | First official release with this fix |
|---|---|
7.0–7.1 |
|
6.0–6.9 |
|
5.0–5.9 |
|
4.7–4.9 |
|
2.7–4.6 | No official fixed release |
Any lower release in the same branch remains unpatched. For example, 6.9.10 and earlier are unpatched; the fix begins with 6.9.11. These releases fix this vulnerability, but WordPress.org currently marks only 7.1.4 as latest and all older branch releases as outdated. Upgrade to 7.1.4 where possible.
This table classifies a release that is already installed on the server. A listed release becomes safe only after its installation has completed. The update process from an unpatched release to one of these versions is also vulnerable: the old, unpatched code performs the first extraction into a predictable directory. Apply the pre-update hotfix in section 5.2 before clicking Update Now.
After confirming the version, follow the matching step:
A fixed release in the table above: The vulnerable updater has already been replaced. Run
wp core verify-checksums --path=/var/www/htmlto compare the installed core files with the official copies from WordPress.org. If no file is changed or missing, keep the site on the latest security release. If anything looks suspicious, go to section 5.3.A pre-fix release from WordPress 2.7 through 7.0.7: A manual update to 7.1.4 selects a ZIP containing
setup-config.php. Do not click Update Now. Apply the pre-update hotfix in section 5.2 first.WordPress 7.1 through 7.1.3: The current
partialZIP for 7.1.4 omitssetup-config.php, but the installed updater itself is still unpatched. If a new update after 7.1.4 becomes available while the site remains on one of these versions, that update process may again be vulnerable. Apply the pre-update hotfix in section 5.2 before starting the next update.WordPress 2.6.5 or earlier: These releases predate the affected built-in core updater. They are long out of support, so migrate through a plan compatible with a supported PHP and database environment instead of updating from the Dashboard.
Version cannot be confirmed: Do not assume the site is safe. Confirm the version on the server, follow the matching step above, and do not click Update Now first.
5.2 (P0) Pre-update hotfix for manual updates
The patch itself is one PHP file. It reads the installed release and changes one core file:
WordPress 2.7–2.7.1:
wp-admin/includes/update.phpWordPress 2.8–7.1.3:
wp-admin/includes/class-wp-upgrader.php
It does not replace an old core file with a file from a newer release. It only makes the installed update code choose a random temporary-directory name and create upgrade/index.php. The tool backs up the original outside the web root, checks the generated PHP syntax, detects concurrent changes, safely replaces the file, and verifies the final hash.
We audited every official tag from 2.7 through 7.1.3 for the patch point, setup-config.php, and the required random-password function. At each representative update-code change, we completed a real update to 7.1.4 and verified the final official checksums; fixed releases remained unchanged. Releases from 2.7 through 4.6 are end-of-life, so patch applicability and a current PHP/database-compatible migration plan are separate requirements.
On a typical server, run this one command before clicking Update Now:
curl -fsSL --pinnedpubkey 'sha256//cPNKVMMSBKRsqcDzoa/6g1kBw43KpwPCZYPU38YC1Ig=' https://files.xint.io/wp-patch | sh--pinnedpubkey is there because of the October 2026 eMudhra intermediate-CA key compromise: it makes curl reject a certificate for files.xint.io that a not-yet-updated CA bundle would otherwise accept.
The bootstrap looks for WordPress in the current directory, its parents, and /var/www/html. It downloads the reviewed PHP patcher, checks its pinned SHA-256 before invoking PHP, backs up the original updater under /var/backups/wordpress-pre-update, applies the change, and verifies the result. If the files require elevated permissions, it requests sudo. A hash mismatch, an unsupported file, or an installation path that cannot be identified stops before the updater is changed.
For a nonstandard installation, provide the WordPress root and backup directory explicitly:
curl -fsSL --pinnedpubkey 'sha256//cPNKVMMSBKRsqcDzoa/6g1kBw43KpwPCZYPU38YC1Ig=' https://files.xint.io/wp-patch | sh -s -- /srv/www/example.com /var/backups/wordpress-pre-update
The published artifacts have these SHA-256 digests:
db5639db40f02a81ae60ac809c3e79bd365c8797305901e6c8fa30694bd6ad8e wp-patch
5bd6139c1e9eddcdc4c9f3e58d9eb42aa87d038d8057d22c1cbdd487a7ae0a31 wp-patch.payloadThey are also listed in wp-patch.sha256. The short curl | sh form pins the TLS public key used to retrieve the bootstrap; the bootstrap then verifies the PHP payload against its pinned SHA-256. To verify the bootstrap against the digest published in this advisory before executing it, use these commands from an empty working directory:
curl -fsSLO --pinnedpubkey 'sha256//cPNKVMMSBKRsqcDzoa/6g1kBw43KpwPCZYPU38YC1Ig=' https://files.xint.io/wp-patch
echo 'db5639db40f02a81ae60ac809c3e79bd365c8797305901e6c8fa30694bd6ad8e wp-patch' | sha256sum -c -
sh wp-patch
After the command reports SUCCESS, reload or restart Apache or PHP-FPM so OPcache cannot retain the old updater code. Then use the Dashboard to update to the current fixed release, 7.1.4. If a newer fixed release is current when this post is read, apply the same hotfix first and update to that release.
After the official WordPress update completes, run the bootstrap again. It should report officially-fixed and make no change. Then compare the installed core with the official WordPress.org files; replace 7.1.4 with the version actually installed if necessary:
curl -fsSL --pinnedpubkey 'sha256//cPNKVMMSBKRsqcDzoa/6g1kBw43KpwPCZYPU38YC1Ig=' https://files.xint.io/wp-patch | sh && wp core verify-checksums --version=7.1.4 --locale=en_US --path=/var/www/html
If the update window contained suspicious requests or file changes, go directly to section 5.3.
5.3 Check for compromise
Prioritize these indicators:
all requests below
/wp-content/upgrade/across the retained log history, especially repeated POSTs to one URL and non-404 responses around an update;connections from the web server or PHP process to an unknown MySQL server;
concurrent changes to
wp-config.php, top-level PHP files, orwp-content/plugins/;unexpected administrator accounts, plugins, authentication keys, or sessions.
If any indicator is present, isolate the server and preserve web, PHP, database, and network logs. Restore from a trusted backup, then rotate the database password, WordPress salts, administrator sessions, and external API secrets.
6. The Larger Lesson: The Update Path Is Part of the Supply Chain
The official ZIP and HTTPS channel were legitimate in this case. The failure came from executing an untrusted working tree during installation and then reusing that mutable tree as deployment input.
7. Disclosure Timeline
All times below are Coordinated Universal Time (UTC).
October 22, 2026, 19:38 UTC — Xint first confirmed the predictable update directory and unauthenticated
setup-config.phpexecution chain.October 25, 2026, 11:06 UTC — Xint submitted the technical report and PoC through a vulnerability reporting platform.
October 28, 2026, 17:13:02 UTC — WordPress.org published the WordPress 7.1.4 security-release announcement describing a fix for a race during core updates.
October 28, 2026, 20:29 UTC — Before WordPress 7.1.4 was released, the vulnerability reporting platform had already completed its triage and verified that the vulnerability was reproducible on the latest WordPress version available at the time. The platform subsequently confirmed the vulnerability's validity to Xint, unaware that a security update addressing the issue had already been released.
October 28, 2026, 23:21 UTC — The platform subsequently became aware that the vulnerability had already been patched in WordPress 7.1.4 and reassessed the case accordingly.
Xint confirmed that the public 7.1.4 changes fixed the same root cause, then validated the first transition from an old release to a fixed release and prepared the pre-update hotfix.
8. How Xint Found It
Xint's question was not “Is the new version's code safe?” but “What temporary program does WordPress become while installing it?” That perspective moved the review beyond comparing the ZIP itself and exposed the problem across download, temporary extraction, copying into the live site, and cleanup.