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

CVE-2023-47822

HIGH · 8.8 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 4.10.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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 allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects MP3 Audio Player for Music, Radio & Podcast by Sonaar: from n/a through 4.10.

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

This is a Missing Authorization vulnerability in the Sonaar MP3 Audio Player WordPress plugin (versions through 4.10). The plugin fails to properly enforce authorization checks, allowing attackers to exploit incorrectly configured access control security levels. This could permit unauthorized users to access or modify functionality they should not have permission to use.

MitigationUpdate the MP3 Audio Player for Music, Radio & Podcast by Sonaar plugin to the latest version immediately. Review and enforce proper authorization checks on all sensitive endpoints and functions within the plugin.

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:< 4.10.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
High
Integrity
High
Availability
High

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

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 the installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > look for 'MP3 Audio Player for Music, Radio & Podcast by Sonaar' and note the version number displayed, or inspect the plugin header in wp-content/plugins/ajax-mp3-player/ajax-mp3-player.php
    Affected if The displayed version is lower than 4.10.1 (for example, 4.10, 4.9, 4.8, etc.)
  2. Verify the plugin is active
    Confirm the Sonaar MP3 Audio Player plugin is currently activated in the WordPress plugins list
    Affected if The plugin shows as 'Active' and the version is below 4.10.1
  3. Inspect access control configuration
    Review the plugin settings under the plugin's admin menu options, looking for any security-related access control, permission level, or user role settings that may be misconfigured
    Affected if Access control settings exist and appear to allow lower-privileged users (such as subscribers or visitors) to access admin-level functionality
  4. Test sensitive endpoint accessibility
    If you have access to the site's API or admin-ajax.php endpoints used by this plugin, attempt a request with a low-privilege user account or unauthenticated request to determine if authorization is properly enforced
    Affected if Requests from unauthorized or low-privilege users return data or allow actions that should require higher permissions

Your environment is affected if the Sonaar MP3 Audio Player plugin version is below 4.10.1 and the plugin is active.

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 4.10.1 or later
Fixed in 4.10.1
Interim mitigation

Update the MP3 Audio Player for Music, Radio & Podcast by Sonaar plugin to the latest version immediately. Review and enforce proper authorization checks on all sensitive endpoints and functions within the plugin.

Recommended fix High confidence

4.10.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 4.10.1 or later.
  6. 6. Alternatively, you can download version 4.10.1 from the official WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin is running version 4.10.1 or higher under Plugins > Installed Plugins.

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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 locally
dbcve dependency scanner

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