Radio PlayerWordPress extension · Softlabbd
CVE-2024-29811
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in SoftLab Radio Player allows Stored XSS.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 confidenceSoftLab Radio Player versions up to 2.0.73 contain a stored Cross-site Scripting (XSS) vulnerability where user-supplied input is not properly sanitized before being rendered in web pages. This allows attackers to inject malicious JavaScript code that persists on the server and executes in the browsers of other users who view the affected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Radio PlayerWordPress extension
<= 2.0.73CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 installationLocate the web application files - common paths include /var/www/html/, /www/, or the document root of the web server. Look for files named 'radio-player', 'player', or similar directories containing 'SoftLab' or 'softlabbd' in the application structure.Affected if The application directory contains SoftLab Radio Player files and the version is 2.0.73 or lower.
-
Determine installed versionCheck for a version file, about page, or configuration file within the application. Common locations include: version.php, about.php, config.php, or the main index.php header section. Look for a string like 'version 2.0.x' or 'v2.0.x'.Affected if The discovered version number is 2.0.73 or any version below it.
-
Identify user input entry pointsReview the application's source code for forms, input fields, or parameters that accept user data and are stored in a database or file system. Focus on features like station name, description, playlist, or any field that displays user content back to visitors.Affected if The application accepts and stores user-supplied data without visible sanitization routines in the code.
-
Inspect stored data for malicious payloadsExamine the database (usually MySQL or SQLite) or flat files where user content is saved. Query tables related to stations, playlists, or user submissions. Look for HTML script tags, javascript: URIs, or event handler attributes in the stored values.Affected if Stored records contain unsanitized HTML script tags, img onerror attributes, or other XSS payloads in fields that render to other users.
-
Verify CSP header configurationCheck if the web server (Apache/Nginx) or application sends Content-Security-Policy headers. Inspect HTTP responses from the application using browser dev tools or curl -I command. Look for 'Content-Security-Policy' or 'X-Content-Security-Policy' headers.Affected if No CSP header is present, or CSP allows inline scripts (unsafe-inline), which would enable XSS execution.
You are affected if SoftLab Radio Player version 2.0.73 or lower is installed and any user input fields store content that gets rendered to other users without sanitization or CSP protection.
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 context-aware output encoding and input validation/sanitization for all user-supplied data before rendering in HTML. Apply Content Security Policy headers to mitigate XSS execution. For a comprehensive fix, upgrade to the latest version if a patch is available and conduct thorough testing to verify all injection points are remediated.
2.0.74 or later
- 1. Back up your WordPress site and database before making any changes
- 2. Navigate to the WordPress admin dashboard
- 3. Go to Plugins > Installed Plugins
- 4. Find 'Radio Player' in the plugin list
- 5. Click 'Update Now' if an update is available, or manually download version 2.0.74 or later from the WordPress plugin repository
- 6. Verify the update completes successfully
- 7. Test the Radio Player functionality on your site to ensure it works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Radio Player
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29811 — 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-29811 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