CVE-2026-4302 json
WowOptin: Next-Gen Popup Maker <= 1.4.29 - Unauthenticated Server-Side Request Forgery via 'link' Parameter in REST API
published 7mo ago modified 4mo ago also EUVD-2026-13980
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
The WowOptin: Next-Gen Popup Maker plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.4.29. This is due to the plugin exposing a publicly accessible REST API endpoint (optn/v1/integration-action) with a permission_callback of __return_true that passes user-supplied URLs directly to wp_remote_get() and wp_remote_post() in the Webhook::add_subscriber() method without any URL validation or restriction. The plugin does not use wp_safe_remote_get/post which provide built-in SSRF protection. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application, which can be used to query and modify information from internal services.
Is CVE-2026-4302 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- wpxpo WowOptin: Next-Gen Popup Maker – Create Stunning Popups and Optins for Lead Generation
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/b1c3e480-0221-4913-bcce-f34ded9edca8?source=cve
- plugins.trac.wordpress.org /browser/optin/trunk/includes/integrations/implementations/class-webhook.php#L38
- plugins.trac.wordpress.org /browser/optin/tags/1.4.23/includes/integrations/implementations/class-webhook.php#L38
- plugins.trac.wordpress.org /browser/optin/trunk/includes/integrations/implementations/class-webhook.php#L45
- plugins.trac.wordpress.org /browser/optin/tags/1.4.23/includes/integrations/implementations/class-webhook.php#L45
- plugins.trac.wordpress.org /browser/optin/trunk/frontend/class-rest-frontend.php#L55
- plugins.trac.wordpress.org /browser/optin/tags/1.4.23/frontend/class-rest-frontend.php#L55
- plugins.trac.wordpress.org /browser/optin/trunk/frontend/class-rest-frontend.php#L44
- plugins.trac.wordpress.org /browser/optin/tags/1.4.23/frontend/class-rest-frontend.php#L44
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3484392%40optin&new=3484392%40optin&sfp_email=&sfph_mail=
Sources
- CVE List CVE-2026-4302
- NVD CVE-2026-4302
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.