dbcve.org
Mp3 Audio Player For Music\, Radio \& PodcastWordPress extension · Sonaar

CVE-2024-30530

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-31
Fix available
A fix is available. Upgrade to 5.1.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Sonaar Music MP3 Audio Player for Music, Radio & Podcast by Sonaar allows Stored XSS.This issue affects MP3 Audio Player for Music, Radio & Podcast by Sonaar: from n/a through 5.1.

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 confidence

A Stored Cross-Site Scripting (XSS) vulnerability in the Sonaar MP3 Audio Player plugin for WordPress allows authenticated attackers to inject malicious JavaScript payloads through unsanitized input fields. When users view content containing the injected script, it executes in their browser, potentially stealing session cookies or performing actions on behalf of the victim.

MitigationUpdate to the latest version of the MP3 Audio Player plugin which includes proper input sanitization and output encoding. Until an update is available, implement output encoding for all user-supplied data before rendering in HTML contexts and consider adding Content-Security-Policy headers.

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
Mp3 Audio Player For Music\, Radio \& PodcastWordPress extension
Affected:< 5.1.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check plugin version in WordPress admin
    Navigate to WP Admin > Plugins > Installed Plugins. Locate 'Sonaar Mp3 Audio Player For Music, Radio & Podcast' and read the version number displayed under the plugin name.
    Affected if The version listed is lower than 5.1.1 (e.g., 5.1.0, 5.0.9, etc.)
  2. Check plugin version via filesystem
    Access the WordPress wp-content/plugins directory. Locate the sonaar-mp3-player folder and open the main plugin PHP file (e.g., sonaar-mp3-player.php) to find the version defined in the plugin header.
    Affected if The version constant or header shows a number less than 5.1.1
  3. Verify plugin is active
    In WordPress admin, confirm the Sonaar MP3 Audio Player plugin shows as 'Active' under the Plugins list.
    Affected if Plugin is active AND version is below 5.1.1 - only active installations with vulnerable versions are affected
  4. Identify exposed input fields
    Check if any Sonaar shortcodes or widget configurations are in use on the site (Pages > All Pages, Posts > All Posts, or Appearance > Widgets). Look for sonaar_player shortcode or audio player widget instances.
    Affected if Plugin is active, vulnerable version, AND any player shortcodes/widgets are published on the site - this creates the attack surface for XSS injection

You are affected if the Sonaar MP3 Audio Player plugin is active and the installed version is below 5.1.1, with any player configurations present on the site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.1.1 or later
Fixed in 5.1.1
Interim mitigation

Update to the latest version of the MP3 Audio Player plugin which includes proper input sanitization and output encoding. Until an update is available, implement output encoding for all user-supplied data before rendering in HTML contexts and consider adding Content-Security-Policy headers.

Recommended fix High confidence

5.1.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Mp3 Audio Player For Music, Radio & Podcast' (Sonaar Music)
  4. Click 'Update now' if an update is available, or deactivate the vulnerable version and install version 5.1.1
  5. Verify the plugin version is 5.1.1 or higher after updating
  6. Test the affected functionality to confirm the XSS vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mp3 Audio Player For Music\, Radio \& Podcast Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30530 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-30530 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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