Security readout for executives and security teams
Plain-English summary
CVE-2024-54385 is an SSRF flaw in the WordPress Radio Player plugin. A vulnerable site could be abused to make server-side requests on an attacker's behalf, potentially exposing limited internal data or affecting trusted back-end interactions. The listed severity is high, with no KEV evidence of active exploitation in the provided sources.
Executive priority
Treat this as a high-priority WordPress plugin exposure review, especially for public sites. It is not confirmed as actively exploited in the provided evidence, but unauthenticated SSRF can create internal access and data-risk pathways. Prioritize inventory, vendor guidance, and removal or update decisions.
Technical view
The issue is CWE-918 Server-Side Request Forgery in princeahmed Radio Player, package radio-player, affecting versions through <= 2.0.83 per the CVE bundle. CVSS 3.1 is 7.2: network exploitable, low complexity, no privileges, no user interaction, scope changed, low confidentiality and integrity impact, no availability impact.
Likely exposure
Exposure is likely limited to WordPress sites with the Radio Player plugin installed and running at versions through 2.0.83. Internet-facing WordPress instances should be prioritized for inventory checks. The provided affected metadata is sparse and includes a version-reference inconsistency, so confirm against vendor or Patchstack records.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The CVSS vector indicates unauthenticated network reachability without user interaction, which increases practical risk, but the bundle does not provide exploit details, vulnerable endpoints, proof-of-concept status, or observed attack activity.
Researcher notes
Evidence is limited to CVE and Patchstack references. The bundle says affected through <= 2.0.83, while the Patchstack URL title references 2.0.82. Do not assume a fixed version, endpoint, or exploitability beyond the CVSS and SSRF classification without checking the advisory directly.
Mitigation direction
- Identify all WordPress sites using the Radio Player plugin.
- Check vendor and Patchstack guidance for the confirmed fixed version or workaround.
- Update the plugin if a fixed release is available from trusted sources.
- Disable or remove the plugin where business use is not required.
- Restrict outbound server requests where feasible to reduce SSRF impact.
Validation and detection
- Inventory installed Radio Player plugin versions across WordPress estates.
- Flag versions at or below 2.0.83 for remediation review.
- Review web server and application logs for unusual outbound request patterns.
- Confirm remediation by rechecking plugin version and vendor advisory status.
- Document any exposed sites, business owners, and remediation decisions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-54385 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/radio-player/vulnerability/wordpress-radio-player-plugin-2-0-82-server-side-request-forgery-ssrf-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.