Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-40300 is a critical-severity SQL Injection (CWE-89) vulnerability in Zohocorp Manageengine Password Manager Pro. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Zoho ManageEngine Password Manager Pro through version 12120 before 12121, PAM360 through 5550 before 5600, and Access Manager Plus through 4304 before 4305 contain multiple SQL injection vulnerabilities tracked as CVE-2022-40300. The issues are classified under CWE-89 and carry a CVSS 3.1 score of 9.8 reflecting network attack vector, low complexity, and no required authentication or user interaction.
An unauthenticated attacker with network access can supply crafted input to trigger the SQL injection flaws, resulting in full compromise of confidentiality, integrity, and availability of the affected password management or privileged access systems. Successful exploitation could allow arbitrary database queries, data exfiltration, or modification of stored credentials and configuration.
Vendor advisories at https://www.manageengine.com/products/passwordmanagerpro/advisory/cve-2022-40300.html describe the affected builds and direct administrators to apply the listed updates that resolve the injections. The associated EPSS score rose from lower values after disclosure to a peak of 0.5295 on 2025-12-11 before receding to the current 0.3825, indicating increased exploitation interest well after the original publication date.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-43597
Vulnerability Data
Zoho ManageEngine Password Manager Pro through 12120 before 12121, PAM360 through 5550 before 5600, and Access Manager Plus through 4304 before 4305 have multiple SQL injection vulnerabilities.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation and sanitization of untrusted input to block the crafted SQL payloads that trigger CVE-2022-40300.
Mandates prompt application of vendor patches that eliminate the SQL injection flaws in the listed ManageEngine builds.
Enforces authentication and authorization checks before any database interaction, limiting the unauthenticated network access path used by the vulnerability.
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 target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.
Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.
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.
The same secure-coding and static-analysis activities surface missing neutralization of SQL metacharacters before the system is accepted.
Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.
Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.
Secure-coding rules and security testing phases mandate the use of parameterized queries or equivalent escaping, preventing the construction of dynamic SQL statements from untrusted input.
Language-specific secure coding rules, peer review and SAST together prevent the construction of SQL statements from untrusted data without proper parameterization or escaping.