CVE-2026-3475: Instant Popup Builder (WordPress plugin) · Missing Authorization
Affects Instant Popup Builder (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 31 Oct 2026, 08:20 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| instantpopupbuilderInstant Popup Builder – Powerful Popup Maker for Opt-ins, Email Newsletters & Lead Generation | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor's advisory for updates. Until a fix is released, consider disabling or restricting access to the affected plugin functionality if possible to reduce exposure.
Description
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/979962e3-9052-4dc9-94d0-3ec8de3d5460?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/instant-popup-builder/trunk/public/class-instant-popup-subscription-public.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/instant-popup-builder/tags/1.1.6/public/class-instant-popup-subscription-public.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/instant-popup-builder/trunk/public/class-instant-popup-subscription-public.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/instant-popup-builder/tags/1.1.6/public/class-instant-popup-subscription-public.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3477334%40instant-popup-builder&new=3477334%40instant-popup-builder&sfp_email=&sfph_mail= (opens in a new tab)