🛡️ CVE-2025-0148 — zoom

How this vulnerability can be exploited

This issue can be reached from an adjacent network, attack complexity is high, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

• Attack vector: Adjacent network — the attacker has to sit on the same local or logical network.
• Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
• Privileges required: None — an unauthenticated stranger can try it.
• User interaction: Required — someone has to click, open or visit something.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
• Integrity impact: None.
• Availability impact: None.

Weakness class

CVE-2025-0148 is classified as CWE-549: Missing Password Field Masking. The product does not mask passwords during entry, increasing the potential for attackers to observe and capture passwords.

Affected software

CVE-2025-0148 is recorded against 2 packages.

• io.jenkins.plugins:zoom (fixed in 1.6)
• unknown

Timeline and source

Published on 4 February 2025 and last revised on 13 March 2025. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

nvd.nist.gov (Advisory)
github.com (Package)
www.zoom.com (Web)

Other advisories for this package

io.jenkins.plugins:zoom has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2025-0142 (published 30 Jan 2025)

Same weakness in other software

These advisories are the same class of weakness (CWE-549: Missing Password Field Masking) in other software:

• CVE-2026-3314 (4.6 Medium, published 26 May 2026)
• CVE-2025-13175 (published 14 Jan 2026)
• CVE-2025-42904 (6.5 Medium, published 9 Dec 2025)
• CVE-2025-64170 (3.8 Low, published 12 Nov 2025)
• CVE-2025-31727 (5.5 Medium, published 2 Apr 2025)
• CVE-2025-31728 (5.5 Medium, published 2 Apr 2025)
• CVE-2025-30197 (3.1 Low, published 19 Mar 2025)
• CVE-2024-10122 (2.7 Low, published 18 Oct 2024)

Details

Affected Packages

References