dbcve.org
ZoomsoundsWordPress extension · Digitalzoomstudio

CVE-2025-3431

HIGH · 7.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to after 6.91 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
The ZoomSounds - WordPress Wave Audio Player with Playlist plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 6.91 via the 'dzsap_download' action. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.

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 ZoomSounds WordPress plugin versions up to 6.91 contains an Arbitrary File Read vulnerability in the 'dzsap_download' action. This endpoint lacks proper input validation, allowing unauthenticated attackers to supply path traversal sequences to read sensitive files from the server filesystem such as wp-config.php, passwd files, or other configuration data.

MitigationUpdate the ZoomSounds plugin to version 6.92 or later once released. If no patched version is available, disable the plugin immediately. Review server file permissions and consider implementing Web Application Firewall rules to block path traversal patterns as a temporary mitigation.

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
ZoomsoundsWordPress extension
Affected:<= 6.91

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. Check if ZoomSounds plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Zoomsounds' or 'Digitalzoomstudio Zoomsounds' in the plugin list.
    Affected if The ZoomSounds plugin appears in the installed plugins list
  2. Identify the installed ZoomSounds version
    In the Plugins list, click on the Zoomsounds plugin to view details, or check the plugin files in wp-content/plugins/dzsap/ for a version indicator (often in main PHP file or readme.txt). Compare the version number to 6.91.
    Affected if The installed version is 6.91 or lower
  3. Verify the vulnerable dzsap_download endpoint is accessible
    Check if the WordPress site responds to requests at /wp-admin/admin-ajax.php?action=dzsap_download. This endpoint should exist if the plugin is active. Use a tool like curl to test: curl -s -o /dev/null -w '%{http_code}' 'https://SITEURL/wp-admin/admin-ajax.php?action=dzsap_download'
    Affected if The endpoint returns any HTTP response (not 404), indicating the vulnerable action is registered
  4. Test for path traversal vulnerability (optional, requires caution)
    If authorized and safe to do so, send a request with path traversal sequences to the endpoint, such as: curl 'https://SITEURL/wp-admin/admin-ajax.php?action=dzsap_download&file=../../wp-config.php'. A successful exploit would return file contents.
    Affected if The server returns the contents of files outside the intended directory, confirming the path traversal vulnerability is exploitable

A user is affected if the ZoomSounds plugin (version 6.91 or lower) is installed and active, with the dzsap_download endpoint accessible and vulnerable to path traversal.

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.

From vendor data
Upgrade available Upgrade to a release after 6.91
Interim mitigation

Update the ZoomSounds plugin to version 6.92 or later once released. If no patched version is available, disable the plugin immediately. Review server file permissions and consider implementing Web Application Firewall rules to block path traversal patterns as a temporary mitigation.

Fix this in Zoomsounds Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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