Streamcast Radio PlayerWordPress extension · Bplugins
CVE-2021-24416
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 · uneditedThe StreamCast – Radio Player for WordPress plugin before 2.1.1 does not sanitise or validate the parameters from its shortcode, allowing users with a role as low as contributor to set Cross-Site Scripting payload in them which will be triggered in the page/s with the embed malicious shortcode
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 · high confidenceThe StreamCast – Radio Player for WordPress plugin before version 2.1.1 fails to sanitize or validate parameters passed through its shortcode, allowing authenticated users with contributor-level permissions or higher to inject malicious JavaScript via shortcode attributes. This stored XSS payload executes whenever the affected shortcode is rendered on a page.
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
Streamcast Radio PlayerWordPress extension
< 2.1.1CVSS 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.
-
Verify StreamCast plugin is installedLog into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'StreamCast - Radio Player' or 'Streamcast Radio Player' in the list of active plugins.Affected if The plugin is installed and active on the WordPress site.
-
Determine installed plugin versionIn the Plugins list, click on the plugin name to view its details, or look for the version number displayed in the plugin list. Compare this version number to the affected range.Affected if The installed version is less than 2.1.1 (for example, 2.1.0, 2.0.9, etc.).
-
Check for shortcode usage on the siteSearch the WordPress database or content (posts, pages, widgets) for the shortcode pattern [streamcast] or similar variations provided by this plugin. This can be done via WordPress admin search or by querying the wp_posts table.Affected if The shortcode is actively used in any published content on the site.
-
Identify user roles with contributor access or higherNavigate to Users > All Users in WordPress admin. Review the roles assigned to users. Check if any users have 'Contributor', 'Author', 'Editor', or 'Administrator' roles.Affected if There are users with contributor-level permissions or higher who could potentially craft the malicious shortcode.
A site is affected if the StreamCast plugin version is below 2.1.1 AND the shortcode is used in content AND users with contributor-level access exist on the site.
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 · scoped2.1.1
Update the StreamCast – Radio Player plugin to version 2.1.1 or later which implements proper input sanitization and validation for shortcode parameters.
2.1.1
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the StreamCast – Radio Player for WordPress plugin
- Click 'Update Now' if an update is available, or manually update to version 2.1.1 or higher
- Verify the plugin version shows 2.1.1 or later after updating
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Streamcast Radio Player
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24416 — 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-2021-24416 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