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

CVE-2024-13857

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-07
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
The WPGet API – Connect to any external REST API plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.2.10. This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application which 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 · moderate confidence

The WPGet API WordPress plugin allows authenticated administrators to make external web requests from the server. The vulnerability is an SSRF flaw that enables attackers to request arbitrary URLs/internal services, potentially accessing internal infrastructure, bypassing firewalls, or querying sensitive internal APIs.

MitigationUpdate the plugin to version 2.2.11 or later once available. If no patched version exists, restrict administrative access to only trusted users or temporarily disable the plugin until a fix is released.

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. Locate the WPGet API plugin installation
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'wpget-api', 'wpget', or similar. Also check via WordPress admin under Plugins > Installed Plugins.
    Affected if The WPGet API plugin folder exists in the plugins directory.
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually wpget-api.php or similar in the plugin folder) and find the 'Version' header in the plugin comment block at the top. Alternatively, check the readme.txt file in the plugin folder.
    Affected if A version number lower than 2.2.11 is found, or no version is declared.
  3. Confirm the plugin is active
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Verify the WPGet API plugin shows as 'Active'. Alternatively, query the wp_options table for the active_plugins option.
    Affected if The plugin is active and running on the site.
  4. Verify administrative access exists
    Check if any user accounts with Administrator role exist in WordPress (Users > All Users). The vulnerability requires a authenticated administrator to exploit the external request feature.
    Affected if At least one Administrator user account exists on the WordPress site.

If the WPGet API plugin is installed, active, and the version is below 2.2.11 with at least one administrator account present, the site is affected by this SSRF vulnerability.

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

Update the plugin to version 2.2.11 or later once available. If no patched version exists, restrict administrative access to only trusted users or temporarily disable the plugin until a fix is released.

Recommended fix Moderate confidence

2.2.11

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'WPGet API – Connect to any external REST API' plugin
  4. If the plugin shows a newer version available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version is 2.2.11 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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