Latest / Decrypted: The UK Cyber Briefing / The WordPress plugin update banner that could log in as you
Transcript
- 0:03This is Decrypted. Tuesday, the eleventh of August.
- 0:07The WordPress plugin update banner that could log in as you.
- 0:12Wordfence disclosed on Monday that attackers spent the summer inside a small WordPress plugin vendor's infra
- 0:19structure. They didn't rewrite any code.
- 0:23They quietly poisoned a J S O N file that a marketing banner in the plugin's admin screen checks on every pag
- 0:30e load.
- 0:38a web shell. It reached some 350,000 sites running BdThemes' plugin portfolio.
- 0:45That includes Element Pack, with its 100,000-plus installs, and several sibling plugins.
- 0:53WordPress dot org pulled the plugins on 8 August.
- 0:57The underlying flaw is still unpatched.
- 1:01And the infrastructure behind the campaign has been linked to earlier compromises of the Advanced Responsive
- 1:06Video Embedder and OptinMonster plugins this year.
- 1:10WordPress still runs a large share of the world's websites.
- 1:14That includes plenty of UK charity, school and small business sites built on exactly this kind of premium plu
- 1:22gin stack. So this is a supply chain risk worth taking seriously, even if nobody in I T has ever heard of BdTh
- 1:30emes.
- 1:35The mechanism is worth understanding, because it breaks the usual mental model of a supply chain attack.
- 1:42Picture a noticeboard in a shop's staff-only back office.
- 1:47It's only meant to display supplier adverts.
- 1:50But it turns out to be wired directly into the till.
- 1:53Pin the right card to that board, and the till opens.
- 1:57That's what happened here.
- 1:59BdThemes' plugins included a small promotional banner.
- 2:03It fetched a J S O N file from the vendor's cloud storage purely to show upsell adverts inside the WordPress
- 2:11dashboard.
- 2:16Attacker-controlled content in the file could run as JavaScript inside the browser of whoever was logged in.
- 2:23In this context, that's always an administrator.
- 2:27No plugin file on disk changed.
- 2:30So there was nothing for WordPress dot org's review process to catch, because the code doing the damage was n
- 2:36ever submitted for review.
- 2:37It lived in a data file on a storage bucket, fetched fresh every time an admin opened their dashboard.
- 2:44Wordfence traced the flaw to a code change from March 2026.
- 2:49The earliest confirmed exploitation was on 23 June.
- 2:53And finally. The lesson: what you fetch is what you trust.
- 2:58The design failure sits at a boundary the vendor never drew.
- 3:02Content served to sell add-ons, and code allowed to run with administrator privilege, ended up in the same pi
- 3:09pe. Nothing separated the two.
- 3:11Secure by Design would treat any remote content pulled into an authenticated admin session as hostile by def
- 3:19ault. It would be escaped on output.
- 3:21And it would be structurally incapable of executing script, no matter what the J S O N contains or how truste
- 3:28d the source appears.
- 3:35plugin does after installation.
- 3:37That goes double for the charities, agencies and small businesses that stack several premium plugins together
- 3:44. It vets the code you download.
- 3:46It doesn't vet the services that code quietly calls afterwards.
- 3:50So, what should you do this week?
- 3:53Check for unfamiliar admin accounts and unrecognised plugin files.
- 3:58Disable the affected BdThemes plugins until a real patch ships.
- 4:02And treat any "check for updates" or promotional component as its own piece of attack surface, not a footnote
- 4:10.
- 4:15Thanks for listening.