dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-4302

HIGH · 7.2 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WowOptin WordPress plugin exposes a REST API endpoint (optn/v1/integration-action) accessible to anyone without authentication. This endpoint passes user-supplied URLs directly to wp_remote_get() and wp_remote_post() without validation. Because the plugin uses the unsafe wp_remote_* functions instead of wp_safe_remote_* variants, attackers can force the server to make requests to internal network resources, internal services, or arbitrary external locations.

MitigationRestrict the vulnerable REST API endpoint via proper authentication/authorization in the permission_callback, or update to a patched version when available. As defense-in-depth, replace wp_remote_get/post with wp_safe_remote_get/post to leverage WordPress's built-in SSRF protections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WowOptin plugin is installed
    Navigate to WordPress admin > Plugins, or inspect /wp-content/plugins/ directory for wowoptin folder, or query site via WP-CLI: wp plugin list --name=wowoptin
    Affected if Plugin is present in the WordPress installation
  2. Determine installed WowOptin version
    Check plugin header in main file (wp-content/plugins/wowoptin/wowoptin.php) for Version comment, or query via WP-CLI: wp plugin get wowoptin --field=version
    Affected if Version is unknown, unpatched, or lower than patched version (compare against available patch when released)
  3. Confirm REST API endpoint is exposed
    Send unauthenticated request to /wp-json/optn/v1/integration-action (e.g., curl -X POST https://TARGET/wp-json/optn/v1/integration-action -d '{"url":"http://example.com"}')
    Affected if Endpoint returns valid JSON response without requiring authentication (401/403 not returned)
  4. Check plugin code for unsafe wp_remote usage
    Inspect plugin file containing the vulnerable endpoint (look for wp_remote_get or wp_remote_post calls), or grep: grep -r "wp_remote_get\|wp_remote_post" /wp-content/plugins/wowoptin/
    Affected if Code uses wp_remote_get() or wp_remote_post() without wp_safe_remote_* variants and without URL validation on user input

User is affected if WowOptin plugin is installed AND the optn/v1/integration-action REST API endpoint responds to unauthenticated requests AND the plugin uses unsafe wp_remote_* functions without URL validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict the vulnerable REST API endpoint via proper authentication/authorization in the permission_callback, or update to a patched version when available. As defense-in-depth, replace wp_remote_get/post with wp_safe_remote_get/post to leverage WordPress's built-in SSRF protections.

Recommended fix Moderate confidence

WowOptin: Next-Gen Popup Maker version 1.4.30 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WowOptin: Next-Gen Popup Maker' in the plugin list
  4. Check the current installed version (should be 1.4.29 or below)
  5. Update the plugin to the latest available version (1.4.30 or later)
  6. Verify the update was successful and the plugin functions correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4302 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data