dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-1249

MEDIUM · 5.0 CVSS v3.1 Published 2026-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
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
The MP3 Audio Player – Music Player, Podcast Player & Radio by Sonaar plugin for WordPress is vulnerable to Server-Side Request Forgery in versions 5.3 to 5.10 via the 'load_lyrics_ajax_callback' function. This makes it possible for authenticated attackers, with author level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 Server-Side Request Forgery (SSRF) vulnerability in the MP3 Audio Player plugin for WordPress. The flaw exists in the 'load_lyrics_ajax_callback' function, which allows authenticated users with author-level access or higher to cause the server to make arbitrary HTTP requests to internal or external resources, potentially exposing internal services and sensitive data.

MitigationUpdate the plugin to version 5.11 or later. As a temporary workaround, restrict user permissions to below author level until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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. Verify MP3 Audio Player plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate the MP3 Audio Player plugin in the list.
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In the plugin list, view the plugin details or check the main plugin file (typically in wp-content/plugins/mp3-audio-player/) for the version header comment.
    Affected if The version is lower than 5.11 or the version cannot be determined (unlisted, modified, or pre-release)
  3. Confirm WordPress user roles exist at author level or higher
    Navigate to Users > All Users in WordPress admin. Review the role assigned to each user. Users with roles of Author, Editor, Administrator, or any custom role with author-level permissions or higher can trigger the vulnerability.
    Affected if At least one user account has author, editor, or administrator role (or equivalent elevated permissions)
  4. Verify the vulnerable AJAX endpoint is accessible
    The vulnerability exists in the load_lyrics_ajax_callback function. This is accessible via WordPress AJAX at /wp-admin/admin-ajax.php?action=load_lyrics. Check if the site has user accounts with author-level access who could potentially make this AJAX request.
    Affected if The plugin is active, users with author+ permissions exist, and the AJAX functionality is not blocked by server configuration

A user is affected if the MP3 Audio Player plugin is installed with a version below 5.11 AND at least one user account with author-level or higher permissions exists on the WordPress 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 5.11 or later. As a temporary workaround, restrict user permissions to below author level until the patch can be applied.

Recommended fix High confidence

Upgrade to the latest version available in the WordPress plugin repository (version 5.11 or later)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'MP3 Audio Player – Music Player, Podcast Player & Radio by Sonaar'
  4. Check the current version number to confirm it is between 5.3 and 5.10
  5. Navigate to Plugins > Add New > Upload Plugin (or download the update from the WordPress plugin repository)
  6. Upload and install the latest version of the plugin
  7. Verify the update was successful by checking the installed version
Caveat Review plugin settings and custom integrations after upgrading as minor version updates may include functionality changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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