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

CVE-2026-39670

MEDIUM · 6.0 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 →
66/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 Brecht Visual Link Preview visual-link-preview allows Server Side Request Forgery.This issue affects Visual Link Preview: from n/a through <= 2.3.0.

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 Brecht Visual Link Preview plugin versions through 2.3.0 allows attackers to make the server perform requests to internal services, cloud metadata endpoints, or internal network resources by manipulating URL parameters used by the visual-link-preview functionality.

MitigationImplement strict URL validation with allowlist-based filtering to restrict fetched URLs to expected domains, and disable any direct user-controlled URL fetching to internal IP ranges, localhost, or cloud metadata endpoints.

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

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

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. Identify Visual Link Preview plugin installation
    Search your CMS or application for the Visual Link Preview plugin. In WordPress, check wp-content/plugins/. In other systems, search for directories or files containing 'visual-link-preview'. Look in plugin/module lists provided by your package manager.
    Affected if The plugin is present in the installation
  2. Determine installed version
    Open the main plugin file and locate the version declaration (for example, 'Version: x.x.x' in the file header). Check composer.json, package.json, or a dedicated version file if the header is not available.
    Affected if Version cannot be determined or is not documented as patched
  3. Locate the preview request endpoint
    Search the plugin code for endpoints that handle URL preview functionality. Look for REST API routes (wp-json/vlp/*), AJAX handlers (admin-ajax.php?action=vlp_*), or custom PHP handlers that accept URL parameters. Identify the function that processes the user-supplied URL.
    Affected if A preview endpoint exists that accepts URL parameters from users
  4. Examine URL validation in request logic
    Review the code path from the endpoint to the HTTP request function. Search for functions that make outbound requests (curl_exec, file_get_contents, wp_remote_request, GuzzleHttp, requests library). Determine whether user input is passed directly to these functions or filtered through validation first.
    Affected if User-supplied URLs are used in HTTP requests without strict allowlist validation or authentication checks

System is affected if Visual Link Preview plugin is installed and its preview functionality accepts arbitrary URLs from user input without validated allowlisting or authentication.

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

Implement strict URL validation with allowlist-based filtering to restrict fetched URLs to expected domains, and disable any direct user-controlled URL fetching to internal IP ranges, localhost, or cloud metadata endpoints.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version > 2.3.0)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Visual Link Preview' by Brecht
  4. 4. Check the current version number displayed
  5. 5. If the installed version is <= 2.3.0, click 'Update Now' if an update is available, or manually download the latest version from the WordPress plugin repository and upload it

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39670 — 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-39670 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