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

CVE-2025-14627

MEDIUM · 6.4 CVSS v3.1 Published 2026-01-01
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 WP Import – Ultimate CSV XML Importer for WordPress plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 7.35. This is due to inadequate validation of the resolved URL after following Bitly shortlink redirects in the `upload_function()` method. While the initial URL is validated using `wp_http_validate_url()`, when a Bitly shortlink is detected, the `unshorten_bitly_url()` function follows redirects to the final destination URL without re-validating it. This makes it possible for authenticated attackers with Contributor-level access or higher to make the server perform HTTP requests to arbitrary internal endpoints, including localhost, private IP ranges, and cloud metadata services (e.g., 169.254.169.254), potentially exposing sensitive internal data.

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 WP Import plugin fails to re-validate URLs after following Bitly shortlink redirects in the `upload_function()` method. While `wp_http_validate_url()` validates the initial URL, the `unshorten_bitly_url()` function follows redirects to arbitrary destinations without validating the final URL, enabling authenticated Contributors+ to trigger SSRF attacks against internal services like localhost and cloud metadata endpoints (169.254.169.254).

MitigationUpgrade to version 7.36 or later. Until then, restrict the 'import' capability to Administrator-level users only and consider network-level filtering of outbound requests to internal IP ranges.

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 WP Import plugin is installed
    Check the WordPress plugins directory for wp-content/plugins/wp-import/ or view the plugin list at /wp-admin/plugins.php
    Affected if WP Import plugin is present and active in the WordPress installation
  2. Determine installed WP Import version
    Read the version from the plugin header comment in wp-content/plugins/wp-import/wp-import.php or from the 'Version:' field in wp-content/plugins/wp-import/readme.txt
    Affected if Version is less than 7.36 (e.g., 7.35, 7.34, etc.)
  3. Check if lower-privileged users have import capability
    Query the WordPress database: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities'; or inspect role capabilities at /wp-admin/users.php. Look for Contributor, Author, Editor, or custom roles that include the 'import' capability
    Affected if Users with Contributor role or below are granted the 'import' capability
  4. Confirm the upload_function endpoint is accessible
    Verify the WordPress AJAX endpoint /wp-admin/admin-ajax.php is reachable and the 'import' action is registered. Check if the unshorten_bitly_url() function exists in wp-content/plugins/wp-import/includes/
    Affected if The upload_function and unshorten_bitly_url functions are present and callable by users with import capability

Environment is affected if WP Import plugin version is below 7.36 AND users with Contributor-level access or lower have the 'import' capability enabled, allowing them to trigger the vulnerable URL unshortening logic.

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

Upgrade to version 7.36 or later. Until then, restrict the 'import' capability to Administrator-level users only and consider network-level filtering of outbound requests to internal IP ranges.

Recommended fix Moderate confidence

Version 7.36 or later (latest version available on wordpress.org)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WP Import – Ultimate CSV XML Importer for WordPress'
  4. Check the current version number to confirm it is 7.35 or below
  5. If update is available, click 'Update Now' to upgrade to the latest version (7.36 or later)
  6. Alternatively, navigate to Plugins > Add New > Upload and upload the latest version from wordpress.org/plugins/wp-import-ultimate-csv-xml-importer
  7. After updating, verify the new version number in the Installed Plugins list

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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