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

CVE-2024-54385

HIGH · 7.2 CVSS v3.1 Published 2024-12-16
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
Server-Side Request Forgery (SSRF) vulnerability in princeahmed Radio Player radio-player allows Server Side Request Forgery.This issue affects Radio Player: from n/a through <= 2.0.83.

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

This is a Server-Side Request Forgery (SSRF) vulnerability in the princeahmed Radio Player WordPress plugin (radio-player) affecting versions up to and including 2.0.83. The vulnerability allows an attacker to make the server perform requests to arbitrary URLs, potentially accessing internal services, cloud metadata endpoints, or bypassing firewall restrictions.

MitigationImplement strict allowlist-based URL validation for any user-controlled input used to make server-side requests, blocking requests to private/internal IP ranges (127.0.0.1, 10.x.x.x, 192.168.x.x,169.254.x.x metadata endpoints) and ensuring requests cannot redirect to internal resources.

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. Locate the radio-player plugin installation
    Check for the plugin directory at /wp-content/plugins/radio-player/ or use WP-CLI: wp plugin list --search=radio-player
    Affected if The plugin directory exists or WP-CLI shows the plugin as installed
  2. Determine the installed version
    Check the main plugin file (usually radio-player.php) for the Version header, or run: grep -i 'Version:' /wp-content/plugins/radio-player/radio-player.php | head -1
    Affected if The version number is 2.0.83 or lower (or if no version is displayed and the plugin is installed, assume affected)
  3. Identify endpoints or settings that accept user-supplied URLs
    Review plugin source code for functions handling HTTP requests (wp_remote_get, wp_remote_post, file_get_contents with URLs, cURL calls) that use user input as the request URL; look in /wp-content/plugins/radio-player/ for ajax handlers or shortcode processing files
    Affected if User-controllable URL input is passed to server-side request functions without proper validation

If radio-player version 2.0.83 or lower is installed AND user-controllable URLs can reach the server-side request functionality, the environment is vulnerable to 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based URL validation for any user-controlled input used to make server-side requests, blocking requests to private/internal IP ranges (127.0.0.1, 10.x.x.x, 192.168.x.x,169.254.x.x metadata endpoints) and ensuring requests cannot redirect to internal resources.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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