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

CVE-2026-4328

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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
The Advanced Import plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.4.6. This is due to the plugin using wp_remote_get() to fetch a user-supplied URL without validating that the URL does not point to internal or private network resources in the demo_download_and_unzip() function. The 'demo_file' parameter from $_POST is passed through sanitize_text_field() (which only handles XSS-related sanitization) and then directly into wp_remote_get() when 'demo_file_type' is set to 'url'. Notably, the plugin uses wp_safe_remote_get() in other locations (theme template libraries) which would provide SSRF protection, but fails to use it in this critical AJAX handler. This makes it possible for authenticated attackers, with Author-level access and above (upload_files capability), to make web requests to arbitrary locations originating from the web application, which can be used to query and view data from internal services, including cloud instance metadata endpoints.

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 Advanced Import WordPress plugin uses wp_remote_get() to fetch user-supplied URLs from the 'demo_file' POST parameter in the demo_download_and_unzip() function without validating against internal/private network resources. Although sanitize_text_field() is applied, it only prevents XSS, not SSRF. When 'demo_file_type' equals 'url', the unsanitized URL is passed to wp_remote_get(), enabling authenticated Author+ users to probe internal services and cloud metadata endpoints.

MitigationReplace wp_remote_get() with wp_safe_remote_get() in the demo_download_and_unzip() function and implement explicit URL allowlist validation to prevent requests to internal/private IP ranges and cloud metadata services.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Advanced Import plugin is installed
    Navigate to WordPress Admin > Plugins and confirm 'Advanced Import' plugin is active. Note the installed version number.
    Affected if Plugin is installed and active with no version constraint (no safe version range provided)
  2. Confirm user role capability
    Check if any user account on the site has Author level or higher privileges. These roles can access the vulnerable demo_download_and_unzip() function via the plugin's import functionality.
    Affected if Any user with Author+ role exists on the site
  3. Identify vulnerable code path
    Inspect the plugin source code (wp-content/plugins/advanced-import or similar) and locate the demo_download_and_unzip() function. Verify it uses wp_remote_get() with the 'demo_file' POST parameter when 'demo_file_type' equals 'url'.
    Affected if Function exists and uses wp_remote_get() without URL allowlist or private IP validation
  4. Test SSRF exposure (authorized only)
    If you have Author+ access, submit a POST request to the plugin's import endpoint with demo_file_type=url and demo_file pointing to an internal IP (e.g., http://127.0.0.1:8080 or http://169.254.169.254) to confirm the plugin makes the request.
    Affected if Plugin successfully fetches internal/private network URLs without blocking

The site is affected if the Advanced Import plugin is installed, the demo_download_and_unzip() function uses wp_remote_get() for URL-type imports, and any user with Author+ role exists who could trigger the SSRF.

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

Replace wp_remote_get() with wp_safe_remote_get() in the demo_download_and_unzip() function and implement explicit URL allowlist validation to prevent requests to internal/private IP ranges and cloud metadata services.

Recommended fix Moderate confidence

Advanced Import plugin version 1.4.7 or later

  1. Update the Advanced Import plugin to version 1.4.7 or later via the WordPress plugin repository or WordPress admin dashboard
  2. Verify the update was applied successfully
  3. If immediate update is not possible, manually edit the plugin file containing demo_download_and_unzip() function and replace wp_remote_get() with wp_safe_remote_get() for the 'demo_file' URL handling when 'demo_file_type' is set to 'url'

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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