Act this weekWhat happenedThe U.S. cybersecurity agency CISA confirmed that hackers are actively exploiting a high-severity flaw in WordPress Core during full software upgrades.
Who is affectedAnyone who runs a WordPress website, including small businesses, shops and blogs, and the government agencies ordered to patch.
What to do- 1Update WordPress to the latest patched version as soon as you can.
- 2Ask your web host or developer to confirm the fix is installed.
- 3Check your site for files or changes you do not recognize, especially a setup-config.php file you did not add.
- 4Keep a recent backup so you can restore the site if something looks wrong.
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) says hackers are already using a flaw in WordPress Core, the main software behind WordPress sites. The attacks happen while a site runs a full upgrade. A fix came out late last month.
What changed
The flaw is tracked as CVE-2026-119977 and rated high severity, 8.1 on a 10-point scale. It is a timing problem, called a race condition. During a full upgrade, WordPress uses temporary file locations that are easy to guess and reachable from the web. In that short window, an attacker could run their own code on the server.
No account on the site is needed. CISA added the flaw to its list of known exploited vulnerabilities, which means it has evidence of real attacks.
How big the attacks are
Security firm Wordfence said it recorded more than 18,500 requests aimed at the temporary installer files in the first 21 hours after details went public. It blocked 12,632 attempts in the latest 24 hours. Another firm, Previdian, saw three attempts against its decoy systems on October 30, 2026.
What to do
The alert box above lists the steps. The main one is to update WordPress to the patched version. U.S. federal agencies must apply the fix by November 6, 2026.
The material does not say how many sites have been broken into or who is behind the attacks.
The takeawayIf you run a WordPress site, install the latest patched version now and confirm your host or developer has done the same.