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

CVE-2024-30487

HIGH · 7.6 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to 5.1.1 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

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
Missing Authorization vulnerability in Sonaar Music MP3 Audio Player for Music, Radio & Podcast by Sonaar.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

Missing Authorization vulnerability in the Sonaar MP3 Audio Player WordPress plugin allows unauthenticated or unauthorized users to access protected functionality or data due to absent or insufficient access control checks. This broken access control issue enables attackers to bypass authorization mechanisms and interact with resources they should not have permission to access.

MitigationUpdate the Sonaar MP3 Audio Player plugin to a version beyond 5.1 where authorization checks are properly implemented. If immediate patching is not possible, implement server-level access restrictions or WordPress capability checks as a temporary workaround.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L

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. Identify if Sonaar MP3 Audio Player plugin is installed
    Check for the plugin directory at wp-content/plugins/sonaar-mp3-audio-player/ or run 'wp plugin list' via WP-CLI to enumerate installed plugins
    Affected if The plugin directory or listing does not contain Sonaar MP3 Audio Player
  2. Determine the installed plugin version
    Read the plugin version from the main PHP file header in the plugin directory (commonly sonaar-mp3-audio-player.php) or query it from the WordPress options table
    Affected if The version returned is below 5.1.1 (e.g., 5.1.0, 5.0.x, or older)
  3. Verify the vulnerable authorization check is absent
    Inspect the plugin PHP files for AJAX handlers or admin_init actions that process requests without capability checks (look for current_user_can or nonce verification calls)
    Affected if Functionality handles requests without proper current_user_can() or wp_verify_nonce() validation

A user is affected if the Sonaar MP3 Audio Player plugin version is below 5.1.1 and the plugin is active with unprotected AJAX or admin endpoints accessible to unauthenticated users.

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 the Sonaar MP3 Audio Player plugin to a version beyond 5.1 where authorization checks are properly implemented. If immediate patching is not possible, implement server-level access restrictions or WordPress capability checks as a temporary workaround.

Recommended fix High confidence

5.1.1

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find 'Mp3 Audio Player For Music, Radio & Podcast' (by Sonaar).
  5. 5. If an update is available, click 'Update Now' to upgrade to version 5.1.1.
  6. 6. Alternatively, download version 5.1.1 from the official WordPress repository or Sonaar's website.
  7. 7. Deactivate and delete the current plugin if auto-update fails, then upload and install version 5.1.1.
  8. 8. After updating, verify the plugin is running at version 5.1.1 in the plugins list.

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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30487 — 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-30487 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