CVE-2022-43672
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 · uneditedZoho ManageEngine Password Manager Pro before 12122, PAM360 before 5711, and Access Manager Plus before 4306 allow SQL Injection (in a different software component relative to CVE-2022-43671.
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 confidenceSQL injection vulnerability in Zoho ManageEngine Password Manager Pro, PAM360, and Access Manager Plus allows attackers to inject malicious SQL queries through unsanitized input fields in the application. This can lead to unauthorized database access, data exfiltration, or potential command execution depending on database configuration.
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< 4.3= 4.3< 5.7= 5.7< 12.1= 12.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed productDetermine which Zoho ManageEngine product is deployed: Access Manager Plus, PAM360, or Password Manager Pro. Check running services, installed applications, or product documentation.Affected if Any of these three products is installed.
-
Check Access Manager Plus versionIf Access Manager Plus is installed, locate its version number in the product interface (typically in About or Settings) or check installation directories for version files.Affected if Version is lower than 4.3 or equals 4.3.
-
Check PAM360 versionIf PAM360 is installed, locate its version number in the product interface or check installation directories for version files.Affected if Version is lower than 5.7 or equals 5.7.
-
Check Password Manager Pro versionIf Password Manager Pro is installed, locate its version number in the product interface or check installation directories for version files.Affected if Version is lower than 12.1 or equals 12.1.
The environment is affected if any of the three products is installed and the installed version falls within or below the affected ranges (Access Manager Plus <= 4.3, PAM360 <= 5.7, Password Manager Pro <= 12.1).
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.35.712.1
Upgrade to Password Manager Pro 12122 or later, PAM360 5711 or later, and Access Manager Plus 4306 or later to patch the SQL injection vulnerability.
Password Manager Pro: 12122 | PAM360: 5711 | Access Manager Plus: 4306
- 1. Identify which ManageEngine product is deployed: Access Manager Plus, PAM360, or Password Manager Pro
- 2. Check the current installed version of the product
- 3. For Access Manager Plus: Upgrade to version 4306 or later
- 4. For PAM360: Upgrade to version 5711 or later
- 5. For Password Manager Pro: Upgrade to version 12122 or later
- 6. After upgrade, verify the SQL injection vulnerability is patched by confirming the version number in the product's 'About' or 'License' section
- 7. Review release notes from www.manageengine.com for any additional post-upgrade configuration requirements
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43672 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-43672 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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