dbcve.org
Manageengine Access Manager PlusApplication · Zohocorp

CVE-2022-43671

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-12
Fix available
A fix is available. Upgrade to 4.3 / 5.7 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
Zoho ManageEngine Password Manager Pro before 12122, PAM360 before 5711, and Access Manager Plus before 4306 allow SQL Injection.

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 · moderate confidence

SQL injection vulnerability in Zoho ManageEngine Password Manager Pro (before 12122), PAM360 (before 5711), and Access Manager Plus (before 4306) allows unauthenticated attackers to inject malicious SQL queries through unspecified input vectors, potentially leading to unauthorized database access, data exfiltration, or privilege escalation.

MitigationUpgrade Password Manager Pro to version 12122 or later, PAM360 to version 5711 or later, and Access Manager Plus to version 4306 or later to remediate the SQL injection vulnerability.

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
Manageengine Access Manager PlusApplication
Affected:< 4.3= 4.3
Manageengine Pam360Application
Affected:< 5.7= 5.7
Manageengine Password Manager ProApplication
Affected:< 12.1= 12.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product
    Check which Zoho ManageEngine product is running: Password Manager Pro, PAM360, or Access Manager Plus. Common installation paths include C:\ManageEngine\PasswordManagerPro, C:\ManageEngine\PAM360, or C:\ManageEngine\AccessManagerPlus on Windows, or /opt/ManageEngine/... on Linux. Look for service names or running processes matching these products.
    Affected if Any of these three products is installed and running.
  2. Check Password Manager Pro version
    Locate the version file or check the product UI. The version is typically displayed on the login page footer or in the \conf\version.txt file in the installation directory.
    Affected if The installed version is lower than 12122 or equals 12122.
  3. Check PAM360 version
    Locate the version file or check the product UI. The version is typically displayed on the login page footer or in the \conf\version.txt file in the installation directory.
    Affected if The installed version is lower than 5711 or equals 5711.
  4. Check Access Manager Plus version
    Locate the version file or check the product UI. The version is typically displayed on the login page footer or in the \conf\version.txt file in the installation directory.
    Affected if The installed version is lower than 4306 or equals 4306.
  5. Verify network exposure
    Determine if the product is accessible over the network. Check firewall rules, listener ports (default: 7272 for PMP, 6060 for PAM360, 6181 for Access Manager Plus), and whether the web interface is exposed to untrusted networks.
    Affected if The affected product is network-accessible without proper network segmentation, as the vulnerability allows unauthenticated SQL injection.

You are affected if any of Password Manager Pro (version < 12122 or = 12122), PAM360 (version < 5711 or = 5711), or Access Manager Plus (version < 4306 or = 4306) is installed and network-accessible.

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
Upgrade available Upgrade to 4.3 / 5.7 / 12.1 or later
Fixed in 4.35.712.1
Interim mitigation

Upgrade Password Manager Pro to version 12122 or later, PAM360 to version 5711 or later, and Access Manager Plus to version 4306 or later to remediate the SQL injection vulnerability.

Recommended fix High confidence

Upgrade to Access Manager Plus 4.3 (build 4306), PAM360 5.7 (build 5711), Password Manager Pro 12.1 (build 12122) or later

  1. Identify the currently installed version of the affected product (Access Manager Plus, PAM360, or Password Manager Pro) via the admin console or about page.
  2. Visit the official ManageEngine download page (www.manageengine.com) and obtain the patched builds: Access Manager Plus build 4306 or later, PAM360 build 5711 or later, Password Manager Pro build 12122 or later.
  3. Perform a full backup of the application’s configuration and database.
  4. Stop the ManageEngine service for the product you are upgrading.
  5. Install the downloaded patched version following the vendor’s upgrade instructions (run the installer or apply the patch).
  6. Restart the service after the upgrade completes.
  7. Log in to the admin console and verify the version reflects the patched build (e.g., Access Manager Plus 4.3 build 4306, PAM360 5.7 build 5711, Password Manager Pro 12.1 build 12122).
  8. Run a quick functional test to ensure the application operates normally, and optionally rescan for the SQL injection to confirm remediation.
Caveat No known breaking changes; review release notes for any behavior changes

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

Fix this in Manageengine Access Manager Plus Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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