Running Popup Builder on your site? Check it against CVE-2026-89270 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Popup Builder is in the affected range (≤ 4.4.5), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.
Run the free mini-scan →Popups are annoying right up until they're yours — your signup form, your sale banner, your lead magnet. CVE-2026-89270 is a missing-authorization flaw in the Popup Builder WordPress plugin that lets a visitor with no account at all send every published popup on your site to the trash with a single request. No login, no interaction, nothing to notice until the popups are simply gone.
CVE-2026-89270 is a missing authorization vulnerability (CWE-862) in Popup Builder – Create highly converting, mobile friendly marketing popups by Sygnoos, disclosed October 31, 2026 (CNA: Wordfence). The plugin sits on 200,000+ sites.
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H. Network-reachable, low complexity, no privileges, no user interaction.SGPopup::find() returns false for normally published popups when a sg_popup_preview_id parameter is present, which makes the trash branch fire against every popup simultaneously instead of one. One unauthenticated GET request is the whole attack.Check wp-admin → Plugins for Popup Builder and its version. At 4.4.5 or below, you are in the affected range.
This one is version-checkable, and our scanner checks it: the free mini-scan reads the plugin's public readme and flags a stable tag at or below 4.4.5 as a High finding naming CVE-2026-89270. It reads the version only — it never sends the trashing request, and it never exercises the flaw. A version above the affected range is reported as nothing at all, not as "safe": because the record names no fix, we won't call a newer tag patched on evidence we don't have.
This is an integrity-and-availability flaw, not a data theft — and that's exactly why it slips past triage. A 9.1 with no confidentiality impact reads as "not serious" in a headline scan, right up until a marketing site's entire conversion layer disappears in one request. When an AI builder assembles your stack, every plugin it installs gets write access to something you care about. The inventory question is not just "what can leak?" — it's "what can a stranger change or delete without ever logging in?"
Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the trash check finds a stranger's work.
Running Popup Builder? Update it, check the trash, then run the free check at preshipit.com/free-scan — it flags Popup Builder ≤ 4.4.5 and the rest of your site's exposed surface in about a minute.
Check Popup Builder on your own site — free.
Our free WordPress Plugin Vulnerability Checker pulls Popup Builder's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-89270 included. No scan, no account.
Open the free plugin checker →The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.
New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.
Running Popup Builder on your site? Check it against CVE-2026-89270 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Popup Builder is in the affected range (≤ 4.4.5), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.
Run the free mini-scan →← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report