dbcve.org
Manageengine Pam360Application · Zohocorp

CVE-2024-5546

HIGH · 8.8 CVSS v3.1 Published 2024-08-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Zohocorp ManageEngine Password Manager Pro versions before 12431 and ManageEngine PAM360 versions before 7001 are affected by authenticated SQL Injection vulnerability via a global search option.

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 confidence

Authenticated SQL injection vulnerability in the global search functionality of ManageEngine Password Manager Pro (before version 12431) and PAM360 (before version 7001) allows an authenticated attacker to inject malicious SQL queries, potentially leading to unauthorized database access, data exfiltration, or complete system compromise.

MitigationApply vendor patches: update Password Manager Pro to version 12431 or later, and PAM360 to version 7001 or later. Additionally, restrict access to the global search feature to trusted administrative users only.

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 Pam360Application
Affected:= 4.0= 4.1= 4.5= 5.0= 5.1= 5.2= 5.3= 5.4= 5.5= 5.7= 5.8= 5.9
Manageengine Password Manager ProApplication
Affected:= 6.0= 6.1= 6.2= 6.4= 6.5= 6.6= 6.7= 6.8= 6.9= 7.0= 7.1= 7.5

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 the installed product and version
    Locate the Password Manager Pro or PAM360 installation and retrieve the build number or version. For Password Manager Pro, this is typically shown in the product UI under the About section or in the server details. For PAM360, check the version displayed in the administrator console.
    Affected if The installed version is one of the affected versions: PAM360 versions 4.0 through 5.9 (excluding 6.0), or Password Manager Pro versions 6.0 through 7.5 (excluding later builds).
  2. Determine the build number for Password Manager Pro
    In the Password Manager Pro administrative interface, navigate to the About or System Information section to view the build number. Compare this against build 12431.
    Affected if The build number is below 12431.
  3. Determine the version for PAM360
    In the PAM360 administrative console, locate the version information typically found in the About or Settings area. Compare the version against 7001.
    Affected if The version is below 7001.
  4. Verify if global search functionality is accessible
    Check whether the global search feature is enabled and accessible to authenticated users. This can be confirmed by logging in as a standard user and attempting to access the search functionality, or by reviewing the user role permissions in the administrative console.
    Affected if Global search is enabled and accessible to authenticated users (not restricted to only highly trusted administrators).

You are affected if you are running Password Manager Pro with a build number below 12431, or PAM360 with a version below 7001, and the global search feature is accessible to authenticated users in your environment.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches: update Password Manager Pro to version 12431 or later, and PAM360 to version 7001 or later. Additionally, restrict access to the global search feature to trusted administrative users only.

Recommended fix High confidence

ManageEngine PAM360 version 7001 or later; ManageEngine Password Manager Pro version 12431 or later

  1. 1. Identify the currently installed version of ManageEngine PAM360 or Password Manager Pro
  2. 2. Create a complete backup of the database and configuration files
  3. 3. Download the patched version from the official ManageEngine portal (PAM360 version 7001 or later; Password Manager Pro version 12431 or later)
  4. 4. Stop the ManageEngine service before applying the upgrade
  5. 5. Install the upgraded version following the vendor's migration/upgrade documentation
  6. 6. Verify the upgrade was successful by checking the new version number
  7. 7. Test the global search functionality to confirm the SQL injection vulnerability is resolved
  8. 8. Restart the ManageEngine service
Caveat Standard upgrade risks apply - review vendor release notes for migration considerations and potential configuration changes before proceeding

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

Fix this in Manageengine Pam360 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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