CVE-2024-33592
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 SoftLab Radio Player.This issue affects Radio Player: from n/a through 2.0.73.
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 confidenceServer-Side Request Forgery (SSRF) vulnerability in SoftLab Radio Player allows remote attackers to induce the server to make arbitrary requests to internal or external resources. The vulnerability exists in the URL handling functionality of the radio player application.
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 SoftLab Radio Player installationCheck for SoftLab Radio Player application files in the web server directory, common paths include /var/www/, /htdocs/, or the application-specific installation directory. Look for files named 'radio.php', 'player.php', or a 'softlab' directory.Affected if SoftLab Radio Player is present on the system
-
Determine the installed versionCheck version files such as version.php, CHANGELOG, or a config/version file within the SoftLab Radio Player installation directory. Compare the version string against any officially documented version ranges.Affected if The installed version has no patch applied or is older than the fixed version (check vendor documentation for specific version numbers)
-
Verify URL handling functionality is exposedExamine the web application's routing or endpoint configuration to determine if the radio station URL submission or playlist fetching feature is accessible via HTTP/HTTPS. Look for endpoints that accept URLs as input parameters.Affected if The URL handling feature is accessible over the network without authentication or with weak access controls
-
Inspect URL validation logicReview the source code files that handle URL processing, typically in the main player script or a 'request', 'fetch', or 'stream' module. Look for absence of strict allowlist validation on the URL parameter before making server-side requests.Affected if No strict URL allowlist or protocol validation is implemented in the code handling URL requests
-
Test for SSRF behaviorIf authorized, submit a test URL pointing to an internal resource (such as http://127.0.0.1 or an internal IP) via the radio player URL input field and observe if the server attempts to fetch it.Affected if The server makes requests to arbitrary URLs provided in the input, including internal resources
A user is affected if SoftLab Radio Player is installed with an unpatched version and the URL handling feature is network-accessible without strict validation controls.
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.
dbcve · scopedImplement strict URL validation with allowlist controls, restrict allowed protocols and destinations, and validate all user-supplied URLs before server-side requests.
Any version above 2.0.73 (latest stable release)
- 1. Navigate to the SoftLab Radio Player plugin/theme in your WordPress installation
- 2. Check the current installed version of Radio Player
- 3. Check SoftLab's official WordPress repository or their website for the latest version
- 4. Update Radio Player to the latest available version (any version above 2.0.73)
- 5. Verify the update was successful and test that SSRF protections are functioning
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33592 — 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-2024-33592 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