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

CVE-2024-31343

HIGH · 7.5 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to 5.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 4.10.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 Missing Authorization vulnerability exists in the Sonaar MP3 Audio Player plugin for WordPress (versions through 4.10.1). The vulnerability allows unauthenticated or unauthorized users to access sensitive functionality or data that should require proper authentication and authorization checks. With a CVSS score of 7.5, this represents a high-severity access control failure that could expose administrative or privileged features.

MitigationUpgrade to version 4.10.2 or later which contains the authorization fix, or implement proper capability checks and nonce validation on all sensitive plugin endpoints if a patch is unavailable.

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.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Identify plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Sonaar Mp3 Audio Player For Music, Radio & Podcast'. Note the version number displayed.
    Affected if The plugin is installed and the version listed is below 5.0 (e.g., 4.10.1, 4.9.x, etc.)
  2. Check version via file inspection
    Access the plugin directory via FTP or file manager at wp-content/plugins/sonaar-music. Open the main plugin file (often sonaar-music.php or similar) and locate the 'Version' header comment in the plugin metadata.
    Affected if The version declared in the plugin file is 4.10.1 or earlier, or any version below 5.0
  3. Inspect admin capability checks
    Examine the plugin PHP files for AJAX action handlers (wp_ajax_* and wp_ajax_nopriv_*) and admin page callbacks. Look for missing current_user_can() calls or capability checks before sensitive operations.
    Affected if Sensitive AJAX actions or admin functions are registered without proper capability verification, or nopriv handlers exist for privileged operations
  4. Test unauthenticated endpoint access
    If you have access to the site's AJAX or admin-ajax.php endpoint, attempt to access plugin-specific actions (such as saving settings, exporting data, or modifying player configurations) without providing authentication credentials.
    Affected if The plugin accepts and processes requests from unauthenticated users for functions that should require admin-level permissions
  5. Review nonce validation presence
    Search plugin source code for nonce verification patterns: check_admin_referer(), wp_verify_nonce(), or rest_handle_request(). Identify if these checks are absent on sensitive endpoints.
    Affected if Sensitive actions lack nonce validation or the nonce check can be bypassed, allowing unauthorized requests

You are affected if the Sonaar MP3 Audio Player plugin is installed at version 4.10.1 or any version below 5.0, and the plugin exposes administrative functions or data without requiring authentication or proper capability verification.

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.0 or later
Fixed in 5.0
Interim mitigation

Upgrade to version 4.10.2 or later which contains the authorization fix, or implement proper capability checks and nonce validation on all sensitive plugin endpoints if a patch is unavailable.

Recommended fix High confidence

Version 5.0 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'Mp3 Audio Player For Music, Radio & Podcast' (Sonaar Music)
  4. 4. Check the current installed version number
  5. 5. If the installed version is below 5.0, update the plugin to version 5.0 or later
  6. 6. Verify the update was successful by confirming the new version number

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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