dbcve.org
ZoomsoundsWordPress extension · Digitalzoomstudio

CVE-2025-0839

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-05
Fix available
A fix is available. Upgrade to after 6.91 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via shortcodes in versions up to, and including, 6.91 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 fails to properly sanitize and escape user-supplied attributes in its shortcodes, allowing authenticated users with contributor-level or higher permissions to inject malicious JavaScript that persists on affected pages and executes when viewed.

MitigationUpdate the ZoomSounds plugin to the latest version once available, or implement proper input sanitization (sanitize_text_field, esc_attr) and output escaping (esc_html, esc_js) on all shortcode attributes before rendering.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 ZoomSounds plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Digitalzoomstudio Zoomsounds' or 'Zoomsounds' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'zoomsounds' or 'digitalzoomstudio'.
    Affected if The ZoomSounds plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, click on the ZoomSounds plugin to view its details, or open the main plugin file (usually zoomsounds.php) and look for the 'Version:' header in the plugin comments at the top. Compare this version number to 6.91.
    Affected if The installed version is 6.91 or lower
  3. Identify shortcode usage on the site
    Search the WordPress database (wp_posts table) or site content for the '[zoomsounds' shortcode string. In phpMyAdmin or via WP-CLI: wp db query "SELECT * FROM wp_posts WHERE post_content LIKE '%[zoomsounds%';"
    Affected if Any posts, pages, or custom post types contain the zoomsounds shortcode with user-controlled attributes
  4. Confirm contributor+ user roles exist
    In WordPress admin, go to Users and review user roles. Check for users with 'Contributor', 'Author', 'Editor', or 'Administrator' roles who can create or edit content containing shortcodes.
    Affected if At least one user account has Contributor-level permissions or higher and can create or edit posts/pages

A user is affected if the ZoomSounds plugin version is 6.91 or lower, the plugin is active, and contributor-level or higher users exist who can add shortcode content to 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
Upgrade available Upgrade to a release after 6.91
Interim mitigation

Update the ZoomSounds plugin to the latest version once available, or implement proper input sanitization (sanitize_text_field, esc_attr) and output escaping (esc_html, esc_js) on all shortcode attributes before rendering.

Recommended fix Moderate confidence

Version 6.92 or later (check WordPress plugin repository or vendor for latest release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the ZoomSounds plugin
  4. Check if an update is available (version higher than 6.91)
  5. If an update is available, click 'Update Now' to install the latest version
  6. Verify the update was successful by checking the plugin version

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

Fix this in Zoomsounds Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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