dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-12057

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The WavePlayer WordPress plugin before 3.8.0 does not have authorization in an AJAX action as well as does not validate the file to be copied locally, allowing unauthenticated users to upload arbitrary file on the server and lead to RCE

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 · high confidence

The WavePlayer WordPress plugin before version 3.8.0 contains a critical vulnerability in an AJAX action that lacks both authorization checks and file validation. Unauthenticated attackers can exploit this to copy arbitrary files locally, leading to remote code execution.

MitigationUpdate WavePlayer plugin to version 3.8.0 or later immediately. If updating is not feasible, disable or remove the plugin until a 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm WavePlayer plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WavePlayer' in the list of active or inactive plugins.
    Affected if WavePlayer appears in the plugins list regardless of activation status
  2. Identify the installed WavePlayer version
    In the WordPress admin, locate the WavePlayer plugin in the list and view the version number displayed beneath the plugin name. Alternatively, check the plugin's main PHP file (typically wp-content/plugins/waveplayer/waveplayer.php) and look for the 'Version' header comment.
    Affected if The version number is lower than 3.8.0 or no version is displayed (indicating an old installation)
  3. Verify the AJAX endpoint is accessible
    Send a direct HTTP request to the vulnerable AJAX action endpoint. The endpoint is typically at /wp-admin/admin-ajax.php?action=waveplayer_upload or similar. Use a tool like curl: curl -I 'https://your-site.com/wp-admin/admin-ajax.php?action=waveplayer_upload'
    Affected if The server responds with a valid HTTP status (200 or 400) rather than a 404 or 403, indicating the endpoint exists and is reachable
  4. Check if the upload directory is writable
    Inspect the plugin's upload directory permissions. The default WordPress uploads folder (wp-content/uploads/) should be checked for write permissions accessible by the web server.
    Affected if The uploads directory is writable by the web server user, allowing arbitrary file uploads to succeed if the vulnerability is exploited

A user is affected if WavePlayer is installed with a version lower than 3.8.0 and the plugin's AJAX upload endpoint is accessible and functional 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WavePlayer plugin to version 3.8.0 or later immediately. If updating is not feasible, disable or remove the plugin until a patch can be applied.

Recommended fix High confidence

WavePlayer version 3.8.0

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WavePlayer in the plugin list
  4. Check the current version of WavePlayer installed
  5. If the installed version is before 3.8.0, click 'Update Now' to update to version 3.8.0
  6. Alternatively, navigate to Dashboard > Updates and update all plugins including WavePlayer
  7. Verify the update was successful by checking the plugin version shows 3.8.0 or higher
  8. Confirm the site still functions correctly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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