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

CVE-2025-14613

HIGH · 7.2 CVSS v3.1 Published 2026-01-14
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 GetContentFromURL plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.0. This is due to the plugin using wp_remote_get() instead of wp_safe_remote_get() to fetch content from a user-supplied URL in the 'url' parameter of the [gcfu] shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to make web requests to arbitrary locations originating from the web application and 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 GetContentFromURL WordPress plugin uses wp_remote_get() instead of the safer wp_safe_remote_get() function when processing the 'url' parameter in its [gcfu] shortcode. This allows authenticated attackers with Contributor-level access or higher to supply arbitrary URLs that the server will fetch, potentially reaching internal services, cloud metadata endpoints, or other sensitive resources accessible from the webserver.

MitigationReplace wp_remote_get() with wp_safe_remote_get() in the plugin's shortcode handler to restrict URL fetching to internal WordPress-allowed hosts only, and implement additional allowlist validation for the 'url' parameter.

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 GetContentFromURL plugin installation
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard and look for 'GetContentFromURL' in the list. Alternatively, check the wp-content/plugins directory for a folder named 'getcontentfromurl' or similar.
    Affected if The plugin is installed and appears in the WordPress plugin list.
  2. Confirm plugin is active
    In the Plugins admin page, check if GetContentFromURL shows as 'Active' under the plugin status column.
    Affected if The plugin is currently activated on the WordPress site.
  3. Check installed plugin version
    Click on the plugin name or 'View Details' link in the plugins list to display the version number. Compare this version to any official changelog or release notes for the plugin.
    Affected if The installed version is older than the version that includes the fix for using wp_safe_remote_get().
  4. Identify shortcode registration
    Access the plugin files via FTP or the WordPress file editor (Appearance > Theme File Editor or a plugin file manager). Look for add_shortcode('gcfu', ...) in the main plugin PHP file.
    Affected if The [gcfu] shortcode is registered and the shortcode handler accepts a 'url' parameter.
  5. Inspect URL fetching code in shortcode handler
    Open the shortcode callback function in the plugin PHP file. Search for wp_remote_get() calls that use $_GET, $_POST, or the shortcode attributes array to retrieve the 'url' parameter value.
    Affected if The code uses wp_remote_get() with the 'url' parameter from user input instead of wp_safe_remote_get().

The environment is affected if the GetContentFromURL plugin is active and its [gcfu] shortcode handler uses wp_remote_get() to fetch URLs provided through the shortcode's url parameter.

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

Replace wp_remote_get() with wp_safe_remote_get() in the plugin's shortcode handler to restrict URL fetching to internal WordPress-allowed hosts only, and implement additional allowlist validation for the 'url' parameter.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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