dbcve.org
ZoomsoundsWordPress extension · Digitalzoomstudio

CVE-2024-13777

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-05
Fix available
A fix is available. Upgrade to after 6.91 or later.
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 ZoomSounds - WordPress Wave Audio Player with Playlist plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 6.91 via deserialization of untrusted input from the 'margs' parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

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 up to version 6.91 is vulnerable to PHP Object Injection via deserialization of untrusted input from the 'margs' parameter. This allows unauthenticated attackers to inject arbitrary PHP objects. While the plugin itself contains no POP chain, the vulnerability becomes exploitable for remote code execution if any other installed plugin or theme contains a usable POP chain.

MitigationUpdate to the latest version of the ZoomSounds plugin once available. If no patch exists, remove the plugin entirely. Additionally, audit and update all other plugins and themes to minimize the risk of a POP chain being available for exploitation.

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
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. Verify ZoomSounds plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Zoomsounds' or 'Digitalzoomstudio Zoomsounds'. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'zoomsounds' or 'dzs-zoomsounds'.
    Affected if The ZoomSounds plugin folder exists in the WordPress plugins directory.
  2. Check installed ZoomSounds version
    In WordPress admin, click on the ZoomSounds plugin to view its details, or open the main plugin PHP file (usually dzs-zoomsounds.php or zoomsounds.php) and look for the 'Version' header in the plugin comment block. Compare this version number to the affected range: 6.91 and below.
    Affected if The installed version is 6.91 or lower.
  3. Confirm the margs parameter is reachable
    Test if the WordPress site processes the 'margs' parameter by making a GET or POST request to any ZoomSounds endpoint (such as /wp-admin/admin-ajax.php or front-end ajax handlers) including 'margs' as a parameter. For unauthenticated detection, check if the plugin's AJAX actions are accessible without authentication by reviewing the plugin's registered AJAX hooks in the code.
    Affected if The plugin responds to requests containing the 'margs' parameter without requiring authentication.
  4. Audit for potential POP chain sources
    Review all installed WordPress plugins and themes for known PHP unserialize() calls or unsafe deserialization patterns. Check plugin code for unserialize() usage on user-controlled input, particularly in ajax handlers or front-end endpoints. Common POP chain sources include plugins with unserialize() on $_POST, $_GET, or $_REQUEST parameters.
    Affected if Any other installed plugin or theme contains a deserialization gadget/POP chain that could be triggered via the margs parameter.

You are affected if ZoomSounds plugin version 6.91 or lower is installed AND the margs parameter is processed by the plugin AND a POP chain exists elsewhere in the WordPress installation.

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 to the latest version of the ZoomSounds plugin once available. If no patch exists, remove the plugin entirely. Additionally, audit and update all other plugins and themes to minimize the risk of a POP chain being available for exploitation.

Fix this in Zoomsounds Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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