CVE-2025-30197
Jenkins Zoho Qengine ≤ 1.0.29.vfa_cc23396502
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:NSummary
CVE-2025-30197 is a low-severity Missing Password Field Masking (CWE-549) vulnerability in Jenkins Zoho Qengine. Its CVSS base score is 3.1 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Input Capture (T1056); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-6 (Authentication Feedback) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6782
Vulnerability Data
Jenkins Zoho QEngine Plugin 1.0.29.vfa_cc23396502 and earlier does not mask the QEngine API Key form field, increasing the potential for attackers to observe and capture it.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.2.6
Mitigating Controls (NIST 800-53 r5) AI
IA-6 directly requires obscuring authentication feedback such as password entry, structurally eliminating the exposure described by CWE-549.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper UI controls such as password masking to prevent observation.
Authentication policies cover password handling but the subcategory focuses on credential strength and MFA rather than entry-time masking.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Data masking directly addresses hiding sensitive values such as passwords on user interfaces.
Secure coding practices would include implementing password masking, but the control is broader than this single weakness.
Secure authentication explicitly requires masking of authentication secrets during entry.