CVE-2026-24548
BaseFortify
Publication date: 2026-01-23
Last updated on: 2026-04-28
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| patchstack | radio_player | to 2.0.91 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how this SSRF vulnerability in the Radio Player plugin affects compliance with standards such as GDPR or HIPAA.
Can you explain this vulnerability to me?
CVE-2026-24548 is a Server Side Request Forgery (SSRF) vulnerability in the WordPress Radio Player Plugin versions up to and including 2.0.91. It allows an unauthenticated attacker to make the affected website send HTTP requests to arbitrary domains controlled by the attacker. This means the attacker can trick the server into communicating with other services, potentially accessing sensitive information on the same system as the vulnerable plugin. [1]
How can this vulnerability impact me? :
This vulnerability could allow an attacker to access sensitive information from other services running on the same system as the vulnerable plugin by making the server send unauthorized HTTP requests. Although the CVSS score is 5.4 indicating low impact, exploitation could lead to information disclosure and unauthorized internal network access. No privileges are required to exploit this issue. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this SSRF vulnerability involves monitoring for unusual HTTP requests originating from the WordPress Radio Player plugin to arbitrary external domains. Since the vulnerability allows unauthenticated attackers to trigger HTTP requests to attacker-controlled domains, you can look for outbound HTTP requests from the server to unexpected or suspicious domains. Specific commands are not provided in the resources, but general approaches include inspecting web server logs for unusual outbound requests, using network monitoring tools to detect unexpected HTTP traffic, or employing intrusion detection systems configured to alert on SSRF patterns. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting outbound HTTP requests from the server hosting the WordPress Radio Player plugin to only trusted domains, implementing firewall rules to block unauthorized external requests, and monitoring for suspicious activity. Since no official fix or patched version is currently available, applying network-level controls and monitoring is recommended to reduce the risk of exploitation. [1]