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

CVE-2026-39464

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable 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
Server-Side Request Forgery (SSRF) vulnerability in SeedProd Coming Soon Page, Under Construction & Maintenance Mode by SeedProd coming-soon allows Server Side Request Forgery.This issue affects Coming Soon Page, Under Construction & Maintenance Mode by SeedProd: from n/a through <= 6.19.8.

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 · moderate confidence

Server-Side Request Forgery (SSRF) vulnerability in the SeedProd Coming Soon Page and Maintenance Mode WordPress plugin (versions up to 6.19.8). The vulnerability allows an attacker to make the server perform unintended network requests, potentially accessing internal services or exfiltrating data.

MitigationUpdate to the latest version of SeedProd plugin when available, or disable the plugin until a patch is released. If immediate patching is not possible, restrict outgoing network connections from the web server and monitor for suspicious internal requests.

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
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/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 SeedProd plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'SeedProd Coming Soon Page' or check the /wp-content/plugins/ directory for the seedprod-coming-soon-page folder
    Affected if The SeedProd plugin folder exists in the WordPress installation
  2. Check installed SeedProd version
    In WordPress admin, go to Plugins > Installed Plugins and locate the SeedProd entry to view the version number displayed beneath the plugin name
    Affected if The installed version is 6.19.8 or any earlier version
  3. Confirm plugin is active
    In WordPress admin Plugins list, verify the SeedProd plugin status shows as 'Active'
    Affected if The plugin is activated and running on the site
  4. Identify webhook or external request functionality
    Navigate to SeedProd plugin settings pages (usually under Settings > SeedProd or the plugin's dedicated menu) and look for features such as webhooks, API integrations, URL submissions, or any feature that accepts external URLs for server-side fetching
    Affected if Webhook, API fetch, or URL-request features are present and accessible in the plugin configuration
  5. Review server access logs for suspicious outbound requests
    Examine web server access logs (Apache error.log, Nginx access.log, or WordPress debug.log) for HTTP requests originating from the server to internal infrastructure (e.g., 127.0.0.1, 10.x.x.x, 192.168.x.x) or unexpected external domains that were not initiated by normal user browsing
    Affected if Outbound HTTP requests from the server to internal addresses or unusual external destinations appear in logs

A WordPress site is affected if it has SeedProd Coming Soon Page plugin version 6.19.8 or lower installed and active, with the webhook or external URL request feature accessible to attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of SeedProd plugin when available, or disable the plugin until a patch is released. If immediate patching is not possible, restrict outgoing network connections from the web server and monitor for suspicious internal requests.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.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-39464 — 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-39464 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