dbcve.org
ZoomsoundsWordPress extension · Digitalzoomstudio

CVE-2024-13776

HIGH · 8.1 CVSS v3.1 Published 2025-04-05
Fix available
A fix is available. Upgrade to after 6.91 or later.
See remediation →
87/100
Remediation priority · High
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 ZoomSounds - WordPress Wave Audio Player with Playlist plugin for WordPress is vulnerable to unauthorized modification of data that can lead to a denial of service due to a missing capability check on the 'dzsap_delete_notice' AJAX action in all versions up to, and including, 6.91. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update option values to 'seen' on the WordPress site. This can be leveraged to update an option that would create an error on the site and deny service to legitimate users or be used to set some values to true such as registration. There are several other functions also vulnerable to missing authorization.

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 lack capability checks on multiple AJAX actions including 'dzsap_delete_notice', allowing authenticated users with Subscriber-level access to modify WordPress options arbitrarily. This broken access control enables attackers to toggle settings like user registration or corrupt option values, causing denial of service.

MitigationUpdate the ZoomSounds plugin to version 6.92 or later which includes proper authorization checks. If an update is unavailable, remove the plugin and seek an alternative audio player solution.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Verify ZoomSounds plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Zoomsounds' or 'Digitalzoomstudio Zoomsounds'. Alternatively, check the plugin directory at /wp-content/plugins/ for a folder containing 'dzsap' or 'zoomsounds'.
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin Plugins list, find the ZoomSounds entry and note the version number displayed. Alternatively, check the main plugin file (usually dzsap.php or zoomsounds.php) for the 'Version' header in the plugin comment block.
    Affected if The installed version is 6.91 or lower
  3. Confirm AJAX action is accessible
    Check if the WordPress site responds to the AJAX endpoint /wp-admin/admin-ajax.php with action 'dzsap_delete_notice'. This can be tested by submitting a POST request to admin-ajax.php with action=dzsap_delete_notice. No capability verification should be required.
    Affected if The AJAX action responds without requiring elevated privileges (Subscriber role can trigger it)
  4. Review user role assignments
    In WordPress admin, go to Users > All Users and identify accounts with 'Subscriber' role. The vulnerability allows any authenticated user with Subscriber access to modify options.
    Affected if There are user accounts with Subscriber-level role or lower who have login access

A user is affected if the ZoomSounds plugin version is 6.91 or lower AND the site has at least one user with Subscriber-level access (or any authenticated user role) who can access the vulnerable AJAX action.

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 a release after 6.91
Interim mitigation

Update the ZoomSounds plugin to version 6.92 or later which includes proper authorization checks. If an update is unavailable, remove the plugin and seek an alternative audio player solution.

Recommended fix Moderate confidence

Zoomsounds version 6.92 or latest available version (move to a version newer than 6.91)

  1. Check your current Zoomsounds plugin version in WordPress admin under Plugins > Installed Plugins
  2. Navigate to Plugins > Add New > Upload or update through the WordPress admin to upload the fixed version
  3. After updating, verify the plugin functions correctly by testing audio playback
  4. Confirm that users with Subscriber-level access can no longer access admin AJAX actions without proper authorization

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

Fix this in Zoomsounds 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 the upgrade done

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-2024-13776 — 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-13776 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