Skip to content
CISA warns of attacks exploiting WordPress vulnerability that allows hackers to take control of servers

CISA warns of attacks exploiting WordPress vulnerability that allows hackers to take control of servers

Escudodigital • November 7, 2026

A critical vulnerability in WordPress has put administrators of millions of websites on alert. The Cybersecurity and Infrastructure Security Agency ( CISA ) of the United States has added the flaw, identified as CVE-2026-119977 , to its Known Exploited Vulnerabilities (KEV) catalog, confirming that cybercriminals are already exploiting this error to attack vulnerable installations.

The scale of the problem is related to the widespread use of this content management platform. According to W3Techs data from October 2026, WordPress is present on approximately 39.5% of all websites on the Internet, representing 58.2% of the identified content management systems (CMS) market.

The flaw, discovered by security researcher Umut Bayram of Picus Security , is in the WordPress core update mechanism . It is a Time-of-Check to Time-of-Use (TOCTOU) vulnerability, or race condition, that allows an attacker without credentials to exploit the brief interval during which the system unzips files of a new version in a temporary directory accessible from the Internet.

During this process, the files necessary to install WordPress are temporarily available on a server path. If an attacker manages to anticipate the completion of the update, they can access the provisional installer and manipulate the wp-config.php configuration file , which contains the database connection parameters.

According to the research published by the discoverer of the vulnerability, the attacker can replace this configuration with another that directs WordPress to a database under their control. The platform then interprets this as a new installation and allows the configuration process to begin, creating an admin account and, under certain conditions, installing a malicious plugin capable of executing PHP code on the server.

WordPress released version 7.1.4 on October 28, which includes the fix for this vulnerability, in addition to resolving other security issues. The platform itself recommended installing it immediately. It has also planned the distribution of fixes to branches that can still receive security updates, starting from version 4.7.

However, specialists warn of a particularly relevant circumstance: the patch installation process itself can temporarily reopen the exposure window. This occurs because the update initially runs using the vulnerable version's code before replacing it with the corrected files.

For this reason, experts recommend taking preventive measures before starting the update, including blocking external requests to PHP files hosted in the /wp-content/upgrade/ directory. This way, an attacker is prevented from accessing the temporary installer while the new files are being deployed.

The update should not be the only security step . Administrators should review server access logs to detect suspicious requests to files like setup-config.php within temporary directories, especially during update windows. It is also advisable to check for unknown admin accounts, unauthorized plugins, or unexpected modifications to the wp-config.php file.

If there are signs of intrusion, it will be necessary to investigate the possible compromise of the server and consider renewing database passwords, API keys, and other credentials that the attacker might have accessed.

A critical vulnerability in WordPress has put administrators of millions of websites on alert. The Cybersecurity and Infrastructure Security Agency ( CISA ) of the United States has added the flaw, identified as CVE-2026-119977 , to its Known Exploited Vulnerabilities (KEV) catalog, confirming that cybercriminals are already exploiting this error to attack vulnerable installations.

The scale of the problem is related to the widespread use of this content management platform. According to W3Techs data from October 2026, WordPress is present on approximately 39.5% of all websites on the Internet, representing 58.2% of the identified content management systems (CMS) market.

The flaw, discovered by security researcher Umut Bayram of Picus Security , is in the WordPress core update mechanism . It is a Time-of-Check to Time-of-Use (TOCTOU) vulnerability, or race condition, that allows an attacker without credentials to exploit the brief interval during which the system unzips files of a new version in a temporary directory accessible from the Internet.

During this process, the files necessary to install WordPress are temporarily available on a server path. If an attacker manages to anticipate the completion of the update, they can access the provisional installer and manipulate the wp-config.php configuration file , which contains the database connection parameters.

According to the research published by the discoverer of the vulnerability, the attacker can replace this configuration with another that directs WordPress to a database under their control. The platform then interprets this as a new installation and allows the configuration process to begin, creating an admin account and, under certain conditions, installing a malicious plugin capable of executing PHP code on the server.

WordPress released version 7.1.4 on October 28, which includes the fix for this vulnerability, in addition to resolving other security issues. The platform itself recommended installing it immediately. It has also planned the distribution of fixes to branches that can still receive security updates, starting from version 4.7.

However, specialists warn of a particularly relevant circumstance: the patch installation process itself can temporarily reopen the exposure window. This occurs because the update initially runs using the vulnerable version's code before replacing it with the corrected files.

For this reason, experts recommend taking preventive measures before starting the update, including blocking external requests to PHP files hosted in the /wp-content/upgrade/ directory. This way, an attacker is prevented from accessing the temporary installer while the new files are being deployed.

The update should not be the only security step . Administrators should review server access logs to detect suspicious requests to files like setup-config.php within temporary directories, especially during update windows. It is also advisable to check for unknown admin accounts, unauthorized plugins, or unexpected modifications to the wp-config.php file.

If there are signs of intrusion, it will be necessary to investigate the possible compromise of the server and consider renewing database passwords, API keys, and other credentials that the attacker might have accessed.

Become a premium member for free!

Extracted Entities

Attack Types (1)

Countries (1)

CWE Weaknesses (1)

Domains (1)

MITRE ATT&CK (1)

Platforms (2)