CVE-2026-24548
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 · uneditedServer-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.91.
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 · low confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in the princeahmed Radio Player plugin (radio-player) affecting versions up to and including 2.0.91. The vulnerability allows an attacker to make the server perform unintended requests to internal resources, other servers, or external URLs, potentially exposing internal services or bypassing network restrictions.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if radio-player plugin is installedCheck your WordPress plugins directory or CMS plugin list for 'radio-player' or 'princeahmed Radio Player'. In file systems, look for directories named 'radio-player' under wp-content/plugins/Affected if The radio-player plugin by princeahmed is present in the installation
-
Determine the installed radio-player versionCheck the plugin's main PHP file (usually radio-player.php) for the 'Version' header comment, or inspect the plugin metadata via WordPress admin plugins page, or examine the plugin's readme.txt fileAffected if The reported version is 2.0.91 or lower
-
Verify if URL fetching or remote request features are in useReview the plugin's configuration settings in the WordPress admin panel under the radio-player settings. Look for any fields that accept URLs for stream sources, API endpoints, or external resource linksAffected if URL fields are configured and the plugin makes outbound HTTP requests to user-supplied or configured URLs
-
Inspect server access logs for suspicious outbound requestsReview web server access logs (Apache access_log, Nginx access.log) for requests originating from the web server to internal IP ranges (127.0.0.1, 10.x.x.x, 192.168.x.x) or unusual external destinations that coincide with radio-player usageAffected if The server has made outbound requests to internal resources or unexpected external URLs that were not intentionally initiated by administrators
You are affected if the radio-player plugin version 2.0.91 or lower is installed and the plugin is configured to accept or process URLs for streaming or external resources.
Generated from the published advisory. Verify against your own configuration.
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 dataRemediate by implementing strict URL allowlisting, validating all user-supplied URLs server-side before making requests, and disabling unnecessary URL fetching capabilities. Update to a patched version if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24548 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24548 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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