dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-11760

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 eRoom – Webinar & Meeting Plugin for Zoom, Google Meet, Microsoft Teams plugin for WordPress is vulnerable to exposure of sensitive information in all versions up to, and including, 1.5.6. This is due to the plugin exposing Zoom SDK secret keys in client-side JavaScript within the meeting view template. This makes it possible for unauthenticated attackers to extract the sdk_secret value, which should remain server-side, compromising the security of the Zoom integration and allowing attackers to generate valid JWT signatures for unauthorized meeting access.

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 eRoom WordPress plugin exposes Zoom SDK secret keys (sdk_secret) in client-side JavaScript within the meeting view template. This allows unauthenticated attackers to extract these secrets, which should remain server-side only, enabling them to generate valid JWT signatures for unauthorized meeting access.

MitigationRemove all sdk_secret values from client-side JavaScript and ensure Zoom API credentials are only processed server-side. Update to version 1.5.7 or later once available.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Confirm eRoom plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'eRoom' or check the plugins directory (wp-content/plugins/eroom-zoom-meeting) for the plugin folder
    Affected if The eRoom plugin is present on the WordPress site
  2. Identify the installed eRoom version
    Check the plugin main file (usually eroom-zoom-meeting.php) for the 'Version' header in the plugin comment block, or look at the readme.txt file
    Affected if Version is unknown, older than 1.5.7, or the version cannot be determined (assume affected)
  3. Inspect meeting view page source for exposed secrets
    Visit a meeting view page on the frontend, view the page source (Ctrl+U or right-click > View Page Source), and search for 'sdk_secret' or 'ZoomSdk' in the JavaScript code
    Affected if The string 'sdk_secret' appears in client-side JavaScript code (script tags)
  4. Verify JWT generation is possible from client-side
    In the page source, check if the sdk_secret value is directly used in JavaScript functions that construct JWT tokens or API calls to Zoom
    Affected if The sdk_secret value is visible in JavaScript variables or functions accessible to any page visitor

If the eRoom plugin is installed and sdk_secret values are present in client-side JavaScript on meeting pages, the environment is affected by this vulnerability.

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

Remove all sdk_secret values from client-side JavaScript and ensure Zoom API credentials are only processed server-side. Update to version 1.5.7 or later once available.

Recommended fix Moderate confidence

Latest version after 1.5.6 (check WordPress plugin repository for 1.5.7 or higher)

  1. 1. Log in to the WordPress admin dashboard.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the 'eRoom – Webinar & Meeting Plugin for Zoom, Google Meet, Microsoft Teams' plugin.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. After updating, verify the meeting view template no longer contains the sdk_secret in client-side JavaScript.
  6. 6. Consider regenerating Zoom SDK credentials (API keys/secrets) as a precautionary measure since the secret may have been compromised.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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