On September 14, 2026, attackers tampered with the scripts that email marketing company Brevo serves to customer websites. For about 4.5 hours, around 100,000 sites that embed Brevo forms, the chat widget or the SDK showed visitors a fake Cloudflare check and instructions that installed malware. Logged-in WordPress administrators also had a backdoor plugin added to their sites without being asked.

What is going on

The attackers obtained a hardcoded Cloudflare API key with full permissions. A hardcoded key is a password left inside program code, where it can be found and reused. With it, they ran Cloudflare Workers, small programs that execute at the content delivery network edge, between Brevo's servers and the visitor's browser.

That let them rewrite the Brevo scripts in transit. It is like someone with a master key to the sorting office swapping the contents of letters after they are posted, but before they reach the door.

Visitors were shown a ClickFix page: a fake verification screen that asks you to copy a command and paste it into your own computer. Anyone who followed the instructions installed the malware themselves. For logged-in WordPress admins, the script used their active session to silently install a backdoor plugin called "Web Media Optimizer".

Who is affected

Any site that embedded Brevo's form scripts, chat widget or SDK during the roughly 4.5-hour window on September 14, 2026. WordPress sites are the most exposed, because the attack targeted administrators who were logged in while a Brevo script loaded. The change was made at the CDN edge, so site owners had nothing to patch on their own servers.

What to do now

  1. Open your WordPress plugin list and sort by install date. Remove anything added on September 14, 2026, especially a plugin named "Web Media Optimizer".
  2. Change all administrator passwords, then log out every active session so stolen cookies stop working.
  3. Review user accounts and delete any administrator you do not recognise.
  4. Add Subresource Integrity to third-party scripts where your provider supports it. It is an attribute that tells the browser to refuse a script whose contents have changed.
  5. Search your own code and repositories for hardcoded API keys, and rotate any you find.

How to check your own site

Our free Website Security Check reviews the outside of your site: outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If you want a deeper look after an incident like this, the Full scan adds active OWASP Top 10 testing, port and service checks with CVE matching, WordPress deep scans and exposed-file and secret checks; you can run a full scan once you have verified that you own the site.

Source: BleepingComputer, September 2026.