Skip to content
Laskyr

Plugins · instant-popup-builder · data as of 2026-11-04

Is Instant Popup Builder safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.0.4)

As of 2026-11-04. 1 issue is on record for older versions; version 1.1.8 or newer fixes all of them that state a fix.

Latest version
2.0.4
Last updated
2026-10-14
Active installs
100+
Known issues on record
1
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 7.4+

Launch professional, WordPress-native popups for offers, announcements and email signups without a hosted SaaS account or visitor limits. — by Seventh Sky

What to do

  1. Update to the latest version (2.0.4). Anything older than 1.1.8 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get instant-popup-builder --field=version shows what you run; wp plugin update instant-popup-builder updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 5.3 CVE-2026-3475 · published 2026-03-19

Missing authorization check in Instant Popup Builder (1.1.7 and older)

Affected
1.1.7 and older
Fixed in
1.1.8 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Instant Popup Builder plugin for WordPress is vulnerable to Unauthenticated Arbitrary Shortcode Execution in all versions up to and including 1.1.7. This is due to the handle_email_verification_page() function constructing a shortcode string from user-supplied GET parameters (token, email) and passing it to do_shortcode() without properly sanitizing square bracket characters, combined with missing authorization checks on the init hook. While sanitize_text_field() and esc_attr() are applied, neither function strips or escapes square bracket characters ([ and ]). WordPress's shortcode regex uses [^\]\/]* to match content inside shortcode tags, meaning a ] character in the token value prematurely closes the shortcode tag. This makes it possible for unauthenticated attackers to inject and execute arbitrary registered shortcodes by crafting a malicious token parameter containing ] followed by arbitrary shortcode syntax.

NVD CVE-2026-3475Wordfence advisoryCode change (fix)Plugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Instant Popup Builder vulnerability status badge
<a href="https://laskyr.com/plugins/instant-popup-builder"><img src="https://laskyr.com/plugins/instant-popup-builder/badge.svg" alt="Instant Popup Builder vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit